superforge
SolidConcierge and router for the whole making process, from idea to shipped product. Reads intent, hands the work to the right superforge-* skill (brain, biz, brand, ui, dev, test, debug, roast, verify, handoff), and assigns a model tier per subtask across Claude 5, Gemini 3.6, Codex, and Kimi before any agent is dispatched. Use at the start of any build, or when the request spans several of those areas. Use when the user says "let's build", "I want to make", "help me ship", "where do I start", "何か作りたい", "作って", "どこから始める", "一気に進めたい", or runs /superforge.
Install
Quality Score: 80/100
Skill Content
Details
- Author
- takaoumehara
- Repository
- takaoumehara/superforge-skill
- Created
- 3 days ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
superforge-dev
Build multi-component features by decomposing the work and dispatching subagents, assigning a model tier per subtask across Claude 5, Gemini 3.6, Codex, and Kimi. Proposes Subagents versus Agent Teams topology by task complexity and token cost. Use when the user says "implement", "build this feature", "execute the plan", "in parallel", "dispatch agents", "subagents", "which model should", "実装して", "作って", "並列で", "サブエージェント", "プランを実行", "どのモデルで", or runs /superforge-dev.
forge
Designs Claude Code harness artifacts. One triage ladder picks the right surface (skill, hook, path-scoped rule, CLAUDE.md or AGENTS.md entry, workflow script, subagent, MCP); the stance holds the bar every artifact must clear (a gradeable objective, a gap between the model's default and what the owner wants, and a nameable attention shift; the gap is a new idea or source worth operationalizing, a miscommunication to prevent, or an observed failure); per-surface mechanics live in references. Use for creating, reviewing, or refactoring any of these, for distilling articles or docs into one, for skills that under- or over-trigger, hooks that don't fire or fire too often, bloated CLAUDE.mds, and for deciding which surface a behavior belongs on. Triggers on any work on a skill, hook, rule, CLAUDE.md, AGENTS.md, or workflow orchestration script, including debugging triggering or firing semantics and packaging a /command or plugin.
forge
FORGE protocol — world-class multi-model agent swarm and prompt optimiser. Fable engineers a rubric-driven plan (true goal + success rubric + constraints + risks + minimal-sufficient MECE decomposition); Opus critiques & repairs it for MECE/minimality/critical-path; sub-tasks route by tier+kind with effort scaling and real tool use; a perspective-diverse voter panel (with a soundness veto) verifies; failures escalate UP a tier and re-verify; Fable synthesizes and grades the final answer against the rubric. Cost-aware routing: haiku → sonnet → opus → fable. Runs automatically on every message via the UserPromptSubmit hook, and can be invoked manually as /forge <prompt>.