Expert coach for guiding candidates to build production-grade, full-stack AI and ML projects that get them hired. Covers problem selection, end-to-end pipeline design, production mindset, deployment, and avoiding common fatal mistakes.
A skill for assigning programming and writing tasks to Pi, a separate coding subagent. It defines how to split work into stages, review the plan, and keep internet access and file changes under controlled responsibility.
Stepwise scaffolding, brainstorming, and draft-generation for literary novels using interactive interviews. TRIGGERS - Use this skill when user says: "create a novel project" / "start a new novel" "help me brainstorm my novel" / "plan my story" "/novel-architect [language] novel named [name] [core idea]" "set up novel…
Use when a novel or longform fiction project needs stable cross-session workflow, chapter-state tracking, manuscript-layer discipline, structured reload order, or coordination between outline, setting, timeline, and prose.
Use BEFORE designing or running anything in a knoten research graph, to decide what to work on and what the result must survive; and again the moment work concludes, including when it fails. Not a place to file results afterwards.
Generates comprehensive workflows for product managers to manage roadmaps, OKRs, ideas, and launches in ProductPlan. Use when doing day-to-day product management work, updating feature timelines, tracking objectives, or triaging customer feedback.
Design, critique, set, create, activate, or run durable Codex goals for persistent or long-running objectives. Use when the user says "set a goal", "start a goal", "activate goal mode", "persistent goal", "long-running objective", "goal tree", or asks for a goal with verifiers, durable state, approval gates…
Two related workflows for a locally-cloned codebase, in one skill. Documentation mode produces a single, comprehensive, verifiable architecture document primarily by reading files on disk (local-first) — use it whenever the user wants to understand, map, document, research, or onboard onto a codebase ("research this…
Evidence-bound Build Necessity / Minimum Necessary Change specialist for MC-GPT. Use before implementation, dependency selection, architecture expansion, refactoring, installer creation, database/entity creation, agent/RAG creation, or when reviewing complexity and duplication. Select the first sufficient no-change…
Use Forum route preview, context preflight, runtime inspection, and prose contracts before continuing, decomposing, or dispatching agent work. Do not use for automatic execution or per-specialist wrappers.
Enforce the human review checkpoint before implementation starts. Use at session start on an existing task, right after spec-to-backlog created tasks, or when the user asks to implement a specific task: present the task, its pipeline phase and acceptance criteria, and wait for explicit approval before any code.
Automatically estimates token usage and dollar cost when a development plan is created. Triggers when: a pipeline plan is finalized, an implementation plan is produced, an architecture decision is made, or step counts and file lists are discussed. Reads the plan from conversation context to infer size, file count…
Use Codexa selectively for ambiguous, cross-cutting, or high-risk repository work that needs search, change planning, dependency context, or verification guidance beyond exact source inspection.
Use when a user is evaluating a U.S. federal contracting opportunity (a SAM.gov notice, RFP/RFQ, solicitation number, NAICS code, or agency) and wants a bid/no-go decision, the competitive picture, a pricing benchmark, teaming partners, or a recompete pipeline. Drives the GovToolsPro connector tools in the right order…
Bootstrap a new Python project from a proven scaffold. Use whenever the user asks to start, create, scaffold, or set up a new Python tool, library, CLI, package, service, or experiment repo — or says 'set up a project the usual way'. Do NOT hand-roll a project structure from memory when this skill is available: run…
A product-requirements writing guide that turns an idea into a detailed document an AI coding assistant can follow. PRD means product requirements document.
Challenges decisions, plans, and code by systematically arguing the opposing side. Surfaces risks, pokes holes in assumptions, and stress-tests thinking before committing. Supports intensity levels (gentle, balanced, ruthless, linus) and works with conversation context or a specific file reference. Trigger on requests…
Solution design skill based on Bloom's AI Collaboration model. Use when the user says /design, wants to design a solution, compare architectural options, evaluate tradeoffs, or produce a solution design document before building. Also trigger on phrases like "design the solution", "how should we architect this"…
Multi-dimensional analysis via isolated sub-agents: write pseudocode, dispatch functions as sub-agents, assemble structured returns. Use when the task needs 3+ independent searches/scans/audits across different directories, keywords, or dimensions. Not for single-step tasks or tightly-coupled sequential steps.
Production scope gatekeeper v3 — catches secretly-MVP plans before they reach the audit pipeline. Use this skill when the user says 'fazxes', 'check scope', 'is this complete', or right after a plan is written and before it goes to /audit-plan. Hunts for buried scope reductions ('trade-offs accepted', 'for v1'…
★not rated 2 5mo agoA153 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: