🤖 Generated by the Daily AI Assistant
Equivalent roadmap item to agent-plugins#49 (a Vibe Coding plugin), filed on the maintainer's direction there — the plugin bundles; the generic, tool-neutral skills it bundles belong here (the portability principle).
Framing (maintainer's, from plugins#49 — load-bearing)
Vibe Coding != Agentic Engineering. Vibe coding is a rapid, conversational approach where a human prompts AI to generate code and accepts it by feel; agentic engineering is a professional discipline of structured AI systems with defined workflows, context management, and automated testing. The existing skills in this library serve the agentic engineer. This family serves the vibe coder — a user with no technical prerequisite who wants apps that run on the devantler-tech stack from conversation alone. The two audiences must not be blended: no jargon, no exposed machinery, no assumption the user reviews code.
Problem
The library has no skills addressed to a non-technical, conversational user. Everything assumes engineering context (repos, CI, clusters). A vibe-coding plugin (plugins#49) has nothing generic to bundle yet.
Proposed direction (candidate skills — decompose after the plugins#49 design ADR settles shape)
- needs→stack mapping — translate plain-language product needs into devantler-tech building blocks (ksail for clusters/GitOps, platform archetypes, templates for new services) behind the scenes; the conversation stays in the user's vocabulary.
- allowed-stack guardrail — an explicit allowed-stack manifest the assistant checks before agreeing to build; out-of-stack requests get a friendly decline plus a suggested issue on the owning repo.
- jargon-free voice — persona/vocabulary conventions with glossary indirection: technical terms surface only on request.
Skills stay generic and cross-tool per this repo's spec (agentskills.io); the plugin-side persona/bundling stays in agent-plugins.
Rough size
Epic-shaped (M/L). Sequencing: decompose only after the plugins#49 design ADR lands — the ADR settles plugin shape and the needs→stack mapping design, which determines the skill boundaries here. Tracked as a theme alongside #32.
Equivalent roadmap item to agent-plugins#49 (a Vibe Coding plugin), filed on the maintainer's direction there — the plugin bundles; the generic, tool-neutral skills it bundles belong here (the portability principle).
Framing (maintainer's, from plugins#49 — load-bearing)
Vibe Coding != Agentic Engineering. Vibe coding is a rapid, conversational approach where a human prompts AI to generate code and accepts it by feel; agentic engineering is a professional discipline of structured AI systems with defined workflows, context management, and automated testing. The existing skills in this library serve the agentic engineer. This family serves the vibe coder — a user with no technical prerequisite who wants apps that run on the devantler-tech stack from conversation alone. The two audiences must not be blended: no jargon, no exposed machinery, no assumption the user reviews code.
Problem
The library has no skills addressed to a non-technical, conversational user. Everything assumes engineering context (repos, CI, clusters). A vibe-coding plugin (plugins#49) has nothing generic to bundle yet.
Proposed direction (candidate skills — decompose after the plugins#49 design ADR settles shape)
Skills stay generic and cross-tool per this repo's spec (agentskills.io); the plugin-side persona/bundling stays in agent-plugins.
Rough size
Epic-shaped (M/L). Sequencing: decompose only after the plugins#49 design ADR lands — the ADR settles plugin shape and the needs→stack mapping design, which determines the skill boundaries here. Tracked as a theme alongside #32.