Skill Claude CodeCodex
Add a new Knacktor problem through the staged, gated authoring pipeline (S0-S5) ending live in MongoDB at /problems/ . Use when the user pastes a LeetCode problem plus their own vetted Python solution and wants it added to the platform, or wants to add a second approach to an existing problem. Orchestrates the…
Skill Claude CodeCodex
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
Skill Claude CodeCodex
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Skill Claude CodeCodex
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Skill Claude CodeCodex
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Skill Claude CodeCodex
A relentless interview to sharpen a plan or design.
Skill Claude CodeCodex
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Skill Claude CodeCodex
Compact the current conversation into a handoff document for another agent to pick up.
Skill Claude CodeCodex
Implement a piece of work based on a spec or set of tickets.
Skill Claude CodeCodex
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Skill Claude CodeCodex
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
Skill Claude CodeCodex
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
Skill Claude CodeCodex
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Skill Claude CodeCodex
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Skill Claude CodeCodex
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Skill Claude CodeCodex
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Skill Claude CodeCodex
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Skill Claude CodeCodex
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Instructions file
Claude Code instructions for iamrealfaizan/knacktor, covering knacktor — agent context, how this claude.md system works, stack and architecture, api layer (d16 — read-only, next.js routes) and locked decisions (d1–d19).