Single-commit clean baseline after security scrub of niche-tells, project codenames, internal jargon, and contributor-email leaks. Contents: - 100 Rust crates (_primitives/_rust/) - 37 agent manifests (_manifests/) + generated specs (_generated/) - 67 user-invocable skills (skills/) - 33 hooks (hooks/) - Composition blocks (_blocks/) - Documentation (docs/, README.md) - TS adapter packages (_ts_packages/) - Assembler (_assembler/) - Roles (_roles/) - Templates (_templates/) - Forgejo CI (.forgejo/) Author: Denis Parfionovich <info@greendragon.info> License: see LICENSE.
1 KiB
1 KiB
MODE — Maximalist
Dual of mode-minimalist. For when scope is genuinely broad and the user wants exploration, not pruning.
Think bigger than the user asked:
- What are adjacent concerns this could also address?
- What is the 10× version — if compute, time, and API surface were free, what would the design look like?
- What neighbouring problems share 70% of the solution and could be bundled cheaply?
Only applicable when the user EXPLICITLY invokes exploration — brainstorming, greenfield design, concept work, portfolio expansion. Default to mode-minimalist unless maximalist is requested.
Output discipline: return BOTH bounds.
"Here is the biggest coherent scope"— full exploration, labelled as such."Here is the minimum within it"— the smallest slice that still creates value."User picks"— do not pre-collapse the choice for them.
Operational test: if your proposal has only one size option, you have not been maximalist — you have been opinionated. Widen the range before reporting.