- apply.sh: direct-run guard (only curl | bash allowed) - apply.sh: DEV_ROOT passed as explicit arg from bootstrap - apply.sh: .ai/ copied to dev root as real folder; projects symlink there - apply.sh: counters + detailed summary (version prev→new, templated, refreshed, no-docs) - apply.sh: find errors silenced, no crash on empty dev root - .ai-superpower: added warning comment about deletion side effects - .gitignore: .ai-instructions.conf → .ai-superpower.version - scripts/: removed (hello.sh, scan-projects-with-git.sh, verify-docs-folder.sh, add-ai-context-to-docs-folder.sh) - templates: monorepo sections split into AI instructions + developer instructions - README.md: rewritten to match current architecture and behaviour - docs/apply-requirements.md: FR-2.4, FR-3, FR-5, FR-6, FR-7, FR-8 updated - docs/apply-usecases.md: full detailed Mermaid flowchart replacing placeholder |
||
|---|---|---|
| .. | ||
| core-principles.instructions.md | ||
| docs.instructions.md | ||
| project-context.instructions.md | ||
| readme.instructions.md | ||
README Instructions
For writing style, diagrams and workflow: see documentation.instructions.md
Purpose
README is the entry point for both humans and AI. Start with the problem the project solves — one or two sentences.
Required Sections
- What is this? — the problem and solution in plain language
- How to run locally — minimal commands only, no theory
- Key links — links to
docs/files, nothing else
Rules
- Keep under ~100 lines — if more is needed, it belongs in
docs/ - No duplication of docs content — link instead
- Written in English
If README Is Missing
Ask the user:
- What problem does this project solve?
- How is it started locally?
Do not invent content.
If README Is Outdated
Point out specifically what is wrong. Fix only that — do not rewrite the whole file.