Use Weavatrix Refactor only when the user explicitly requests repository source changes that benefit from a proven refactor workflow: symbol rename, coordinated rename, signature change, symbol edit, selected replacement, import cleanup, file or symbol move planning, deletion readiness, exact plan application, or…
Use when an agent must act at a verified future time and prove it — or timestamp/verify any event — via Clockchain. Covers the zero-creds hosted-MCP alarm flow and the full client-side SDK alarm, plus the operational invariants that prevent early fires and false anchors.
Orchestrate large, multi-stage engineering work with a decision-focused Lead, reusable economy Workers, repository-backed handoffs, and optional host task messaging. Activate only for an explicit $tao command. Do not orchestrate simple local edits or activate merely because this skill is being maintained.
Development workflow. Use when building a feature, creating an MVP, refactoring code, fixing a bug, or any task that involves writing or changing implementation code.
Run a bounded audit-remediation-audit loop for an authorized design set or implementation plan, whether produced as plain documents, OpenSpec artifacts, Superpowers plans, or equivalent formats. Use when one invocation should select DESIGN READY or PLAN READY, normalize artifact roles, apply risk-proportionate review…
Grilling session that walks the design decision tree Socratically and exports it as a self-contained interactive HTML decision form. Use when the user wants a design interview or existing decisions exported as a reviewable HTML decision form; ordinary plan discussion does not require this export workflow.
Ruthlessly eliminate comprehension debt before design or implementation. Use when the developer wants to stress-test a plan, decision, requirement, bug, feature, architecture, or implementation idea. The developer must demonstrate that they understand the problem, constraints, behavior, and consequences in their own…
Phase 0 of any project - fire whenever asked to start, scaffold, set up, or adopt a project ("new Python CLI", "set this repo up properly", "add a frontend stack"). Interview, scaffold via OFFICIAL creators, describe into project.yaml, prove with gates.
Execution-topology selector for non-trivial tasks: decides the simplest sufficient execution shape — a single disciplined loop, a loop with parallel fan-out, or a milestone graph with shared state — states its cost, and executes it. Use whenever the user invokes /occam, or brings a task that is clearly multi-part or…
Stress-test a product decision, PRD, roadmap, experiment, or feature proposal using explicit assumptions, simplicity-first scope, surgical changes, and measurable verification loops. Use when product work is ambiguous, over-scoped, solution-led, risky, or needs a clear go/no-go recommendation.
Use when the user brings messy, layered, scattered, overloaded, or ambiguous context and asks to organize it into a brief. Trigger on notes, transcripts, research dumps, meeting context, strategy thoughts, emails, Slack threads, customer feedback, planning fragments, personal context, or requests like "make sense of…
Run an autonomous iterate-test-replan loop until a multi-step coding task is complete. Use this whenever the user asks Claude Code to work autonomously through a backlog, fix plan, or specification with minimal supervision — phrases like "ralph this", "loop until done", "keep iterating until tests pass", "work…
Take a rough idea, brief, or project sketch and return a clear audience, a concrete pain point, an offer framing, and a ranked first-action plan. Triggers on "I have an idea for X", "help me think through X", "I want to build/launch/start X", "what should I do next with X", or any pasted brief that mentions an…
Use when starting any new app, webapp, API, tool, or side project from scratch - when the user names an idea to build or says new project, scaffold, start a repo, set up a project. Produces a running, git-tracked, Claude-ready project skeleton.
A decision-review process that asks five independent AI agents to examine an important question from different viewpoints, then has a chair agent combine their conclusions. It is designed to reduce agreement bias, where an AI too readily supports the user's apparent preference.
A workflow for adapting the smyslokod-starter project template to a specific product idea. It chooses a depth of setup and uses the template's business and project files as starting context.
Use when repeated delivery failures, disputed acceptance, weak evidence patterns, owner-routing mistakes, or trial observations may need reusable governance improvement.
A structured thinking system based on dialectical analysis and seeking facts before deciding. It focuses on examining opposing forces, identifying the main problem, and acting according to evidence and objective conditions.
Five-question triage for routing AI work to the right architecture — script, algorithmic search, LLM workflow, or autonomous agentic loop — before any agent is built. Use when someone says "let's build an agent for X", when deciding whether a use case actually needs an autonomous agent, when reviewing an agent…
Kickoff protocol for any new project in Claude Code. Trigger this skill whenever the user starts something new, such as a new project, product, service, app, bot, script, MVP, or prototype ("let's build", "starting a new project", "I want to make", "scaffold this", "spin up an app", "new repo"). It runs discovery on…
A tool that turns notes, processes, architecture, or other organized content into a single HTML mind map. The result uses a radial layout with branches, zooming, and drag-to-pan navigation.
★not rated 1 25d agoA66 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: