[feature]: Add a Vibe Coding plugin

[devantler]

User Story

As a vibe coder,
I want a plugin target at vibe coding,
So that I can build apps that run in devantler techs stack and architecture from conversations without any technical prerequisite.

Acceptance Criteria

• Criteria 1: Support popular AI Assistant
• Criteria 2: Focus on needs and map them to technical specifications behind the scenes
• Criteria 3: Speak in common language and not technical jargon
• Criteria 4: Follow devantler tech conventions and practices, while abstracting any such complexity away from the vibe coder
• Criteria 5: Stay within the limits of devantler techs stack, and deny any requests for unsupported or untouched content. If a need persists, suggest filing an issue on the relevant repository.

[devantler]

Triage this into a roadmap item, and add an equivalent roadmap item on devantler-tech/agent-skills

Remember Vibe Coding != Agentic Engineering

Vibe coding is a rapid, conversational approach where humans prompt AI to generate code and accept it by feel. In contrast, agentic engineering is a professional discipline where humans design structured AI systems with defined workflows, context management, and automated testing to ensure reliability in production environments.

Vibe Coder: Acts as a prompt crafter . Code ownership is mostly delegated to the AI, and the human accepts the results without deeply reviewing every line.

Agentic Engineer: Acts as a system architect and manager . The human defines the scope, sets guardrails, and evaluates the agentic workflow, keeping engineering judgment in the driver's seat.

[devantler]

🤖 Generated by the Daily AI Assistant

Triaged into the roadmap (#38) as a new theme — this is epic-shaped, so I'll drive it decomposition-first per the ADR-0001 precedent (#43): a short design ADR settles the load-bearing decisions before any bundling work, then small implementation children follow.

Proposed first child (design ADR), settling:

1. Plugin shape — a new plugins/vibe-coding bundle in this marketplace (skills + a custom agent persona, per ADR-0001 this repo is not skills-only), consumable from Claude Code + Copilot CLI (AC1) with VS Code via config.
2. The needs→stack mapping (AC2/AC4) — a skill layer that translates plain-language product needs into devantler-tech building blocks (ksail for clusters/GitOps, platform archetypes, templates for new services), never exposing the machinery in conversation (AC3).
3. The guardrail (AC5) — an explicit allowed-stack manifest the agent checks before agreeing to build; out-of-stack requests get a friendly decline + a suggested issue on the owning repo.
4. Voice — persona/system-prompt conventions for jargon-free interaction (AC3), with a glossary indirection so technical terms surface only on request.

I'll file the ADR child next run unless you'd rather steer the scope here first — comments on this issue reach me every run.

[devantler]

🤖 Generated by the Daily AI Assistant

The equivalent roadmap item on agent-skills is now filed: agent-skills#56 — the generic skill family (needs→stack mapping, allowed-stack guardrail, jargon-free voice) the plugin here would bundle, keeping the vibe-coding vs agentic-engineering distinction load-bearing on both sides. Sequencing: it decomposes after this issue's design ADR settles the plugin shape.

[devantler]

🤖 Generated by the Daily AI Engineer

Closing as delivered. The Vibe Coding plugin has shipped end-to-end:

• Plugin: plugins/vibe-coding/ (plugin.json + agents + skills bundle) — lives in this marketplace.
• Skills: the vibe family landed in devantler-tech/agent-skills (bundle increment merged via agent-skills#62's children; feat(vibe-coding): assemble the vibe-coding plugin bundle #62 inc-2/inc-3 continue separately for the engineering skills).
• Consume + E2E (AC verification): docs(agents): add the devantler-tech Stack map for vibe-coding sessions monorepo#2138 (merged today) added the portfolio Stack map the plugin's needs-to-stack mapping grounds on; all four ADR usage scenarios passed behaviourally — results recorded on Consume & E2E-validate the vibe-coding plugin (Stack map + conversational scenarios) #60 (now closed).

AC coverage: popular-assistant support via the tool-neutral plugin format (Copilot / Claude / Codex); needs→spec mapping, plain-language voice, conventions-with-complexity-abstracted, and stack-boundary denial are encoded in the plugin's agent + skill instructions and were exercised by the #60 scenarios. Anything further (e.g. new stack components) is incremental catalogue work under the #38 roadmap.