feat(cli): emit rules in Kilo flat builds
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
- Ambito
- build-system, cli
Direzione di ricerca
Start with issue #744 and its Kilo profile, configuration resolution, and runtime contract, then trace aidd framework build --target kilo --flat. Verify the implementation against the acceptance criteria: generated namespaced rules are placed at the profile-resolved location, configuration preserves user instructions, repeated builds are idempotent, and a clean-project archive is discoverable by a supported Kilo runtime.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
Kilo flat support from #744 will make it possible to distribute framework artifacts for Kilo. Canonical plugin rules would still be absent from that output.
This is separate from #788, which guides direct generation inside a host project. This issue distributes canonical plugin rules through aidd framework build --target kilo --flat.
Scope
- Materialize canonical plugin
rules/into namespaced Markdown files under the Kilo rules location resolved by the Kilo profile. - Merge generated rule references into the resolved Kilo project configuration without deleting or reordering user-owned
instructionsentries. - Make repeated builds idempotent and preserve relative paths, rule scope, and existing user configuration.
- Cover empty configuration, existing instructions, repeated builds, and a flat archive installed into a clean project.
Acceptance criteria
- A plugin rule is present in a Kilo flat build at the location returned by the Kilo profile.
- The Kilo configuration references generated rules while preserving every existing user-owned
instructionsentry. - Rebuilding neither duplicates generated entries nor alters user-owned entries.
- The generated rule is discoverable by a supported Kilo runtime.
Dependency
Blocked by #744. That issue owns the Kilo profile, including its configuration resolution and runtime contract; this issue must use that contract rather than duplicate it.
Out of scope
- Direct artifact generation in a project, owned by #788.
- Kilo lifecycle hooks and plugins, owned by #744.
- OpenCode flat output, owned by #789.
- Markdown commands under
.kilo/commands/: Kilo does not document that as a native artifact surface. A future command capability, if needed, requires its own plugin-backed product decision.
- Lingua principale
- TypeScript
- Stelle
- 481
- Fork
- 45
- Merge medio
- 17h 40m
- PR unite (30g)
- 106
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di ai-driven-dev/framework
-
refactor(aidd-orchestrator): the check zone says when to stop, and reviews its axes in one round Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
ai-driven-dev/framework#887 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
ai-driven-dev/framework#873 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
ai-driven-dev/framework#872 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
ai-driven-dev/framework#625 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
ai-driven-dev/framework#467 · 1 commento ·
Tutte le issue di ai-driven-dev/framework
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
[Bug]: Matrix progress drafts fail with "Matrix runtime not initialized" during tool activity Apertabug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
calcite-components needs triage refactor
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
Esri/calcite-design-system#15203 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
danielmiessler/LifeOS#2218 ·