一键导入
这个仓库中的 skills
Use this skill when co-authoring beans and Gherkin scenarios with the user — planning sessions that turn intent into feature files and implementation beans. Covers the partnering craft: investigate before asserting, settle design before drafting, ask vs. decide, recording decisions, and the anti-patterns that wreck planning sessions.
Use this skill when multiple workers (parallel checkouts, separate machines, or human + agent) share a single beans tracker. Covers session close protocol, when to pull, and resolving git conflicts on bean files.
Use this skill when working with c3kit.apron.schema — defining schemas, calling coerce/validate/conform/present, handling errors, or writing custom spec functions. Covers the full API including nested types, entity-level specs, and error handling.
Use this skill when working in projects that depend on c3kit libraries (apron, bucket, wire, scaffold). Covers the schema system, database API, web layer, app lifecycle, and conventions specific to the c3kit ecosystem.
Use this skill when organizing directories, designing namespace boundaries, or deciding what belongs at the top level. Covers Screaming Architecture, domain-as-interface seams (Ports & Adapters at the directory level), and implicit/explicit API pairs.
Use this skill when writing, reviewing, or refactoring Clojure or ClojureScript code. Covers naming, formatting, function design, state management, error handling, threading, and cross-platform conventions.
Use this skill when writing, reviewing, or planning Gherkin feature files (.feature). Covers scenario design, step writing, anti-patterns, and acceptance test strategy.
Use this skill when adding logging to production code or asserting on log output in tests. Covers structured logging, level discipline (info/warn/error/debug), event-keyword conventions (:domain/action), and feature-test assertions on log entries.
Use this skill when extracting helpers, renaming functions, replacing magic numbers, or otherwise restructuring code without changing behavior. Covers extract method/namespace, rename, magic-number-to-constant, and the discipline of rewiring callers immediately.
Use this skill when reviewing code or specs for code smells. Covers dead code, unused bindings, duplication, magic numbers, long parameter lists, god namespaces, sleeping in tests, exception ping-pong, and testing smells (bare assertions, table-driven examples, nested describe).
Use this skill when writing code, fixing bugs, adding features, or refactoring. This skill enforces Test-Driven Development — write a failing test first, make it pass with the simplest code, then refactor. No production code without a failing test.