chore(mcp): tighten plan-instruction to override .md plan habit
The Plans paragraph in the MCP server's _INSTRUCTIONS was a quiet footer ("not in local .md files") that lost to the much louder superpowers brainstorming/writing-plans flow, which terminates by saving to docs/superpowers/specs/*.md and docs/superpowers/plans/*.md. Reorder so start_planning is named as the FIRST action, explicitly override the .md skill paths, and extend the rule to cover specs as well as plans (matches rulebook rule 27).
docs: remove Flutter companion app from project surface
The Flutter app no longer adds value over web/PWA access. Strip the in-repo surface that referenced it:
delete docs/android-app.md
drop README docs-table row and feature-list mention
drop the two Flutter roadmap bullets from docs/features.md
remove the Flutter port subsection from docs/design-system.md
The standalone fabled_app repo is untouched here; archival of that repo is a separate operation.
Verification
CI green on commit fd20b67 (typecheck / lint / tests / image build all ✅).
No backend code changes; no migration; no behavior change to running services.
After deploy: the next MCP reconnect picks up the new prompt; nothing else changes.
Two small docs/prompt changes for production.
## Changes
**`chore(mcp)`: tighten plan-instruction to override .md plan habit**
The Plans paragraph in the MCP server's `_INSTRUCTIONS` was a quiet footer ("not in local .md files") that lost to the much louder superpowers brainstorming/writing-plans flow, which terminates by saving to `docs/superpowers/specs/*.md` and `docs/superpowers/plans/*.md`. Reorder so `start_planning` is named as the FIRST action, explicitly override the .md skill paths, and extend the rule to cover specs as well as plans (matches rulebook rule 27).
**`docs`: remove Flutter companion app from project surface**
The Flutter app no longer adds value over web/PWA access. Strip the in-repo surface that referenced it:
- delete `docs/android-app.md`
- drop README docs-table row and feature-list mention
- drop the two Flutter roadmap bullets from `docs/features.md`
- remove the Flutter port subsection from `docs/design-system.md`
The standalone `fabled_app` repo is untouched here; archival of that repo is a separate operation.
## Verification
- CI green on commit `fd20b67` (typecheck / lint / tests / image build all ✅).
- No backend code changes; no migration; no behavior change to running services.
- After deploy: the next MCP reconnect picks up the new prompt; nothing else changes.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The prior wording ("not in local .md files") was a footer after a
how-to and lost to the much louder superpowers brainstorming /
writing-plans skill flow, which terminates by saving to
docs/superpowers/specs/*.md and docs/superpowers/plans/*.md.
Reorder so start_planning is named as the FIRST action, explicitly
override the .md skill paths, and extend the rule to cover specs as
well as plans (matches the rulebook's rule 27).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The Flutter app (separate fabled_app repo) no longer adds value over
web/PWA access. Strip the in-repo surface that referenced it:
- delete docs/android-app.md
- drop README docs-table row and feature-list mention
- drop the two Flutter roadmap bullets from docs/features.md
- remove the Flutter port subsection from docs/design-system.md
The standalone fabled_app repo is untouched here; archival/deletion
of that repo is a separate decision.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two small docs/prompt changes for production.
Changes
chore(mcp): tighten plan-instruction to override .md plan habitThe Plans paragraph in the MCP server's
_INSTRUCTIONSwas a quiet footer ("not in local .md files") that lost to the much louder superpowers brainstorming/writing-plans flow, which terminates by saving todocs/superpowers/specs/*.mdanddocs/superpowers/plans/*.md. Reorder sostart_planningis named as the FIRST action, explicitly override the .md skill paths, and extend the rule to cover specs as well as plans (matches rulebook rule 27).docs: remove Flutter companion app from project surfaceThe Flutter app no longer adds value over web/PWA access. Strip the in-repo surface that referenced it:
docs/android-app.mddocs/features.mddocs/design-system.mdThe standalone
fabled_apprepo is untouched here; archival of that repo is a separate operation.Verification
fd20b67(typecheck / lint / tests / image build all ✅).🤖 Generated with Claude Code
The prior wording ("not in local .md files") was a footer after a how-to and lost to the much louder superpowers brainstorming / writing-plans skill flow, which terminates by saving to docs/superpowers/specs/*.md and docs/superpowers/plans/*.md. Reorder so start_planning is named as the FIRST action, explicitly override the .md skill paths, and extend the rule to cover specs as well as plans (matches the rulebook's rule 27). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>