role-discipline
SolidALWAYS load at session start; mandatory, never on-demand. After self-attesting, Read references/<role>.md for your role (Product Owner / AI Developer / Architect / Deploy phase) — don't-list + refusal phrasing. Shared-protocol prohibitions and FR-24 digest stay resident; bodies load from references/shared-protocols.md.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- fusebase-dev
- Repository
- fusebase-dev/fusebase-flow
- Created
- 4 months ago
- Last Updated
- 1 weeks ago
- Language
- Shell
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
communication
ALWAYS apply — Mode A on operator chat output (visual, concrete, brief), Mode B on internal-artifact writes (dense, tabular, front-loaded). Mandatory at session start, never on-demand; rules stay resident, examples lazy-load from references/.
reasoning-doctrine
The working method — how to think, stage, self-check, and hold alignment across long tasks without needing reminders. Use this skill on EVERY nontrivial task: analysis, planning, implementation, debugging, document work, reviews, or anything spanning more than a few tool calls or more than one response. Especially mandatory on long-running or multi-stage work, where drift is the primary failure mode. If a task has stages, this skill governs how you move through them.
rc-agents-md
Author lean AGENTS.md/CLAUDE.md instruction files — resident system-prompt context where every line pays rent. Use when writing an agent instruction file from scratch, trimming a bloated one, or gating whether a new rule earns residence and at which scope. Do not use for on-demand skills (rc-skill-best-practices), for measuring what the whole config surface costs in tokens (rc-context-budget), or for human-facing docs and READMEs (rc-readme).