Loading...
Loading...
Found 41 Skills
Adds and enhances comments and documentation comments in code. Use with requests like 'add comments', 'write comments', 'enhance comments', 'add JSDoc', 'add docstring', 'add documentation comments'. Preserve role boundaries from the package/service perspective, prerequisites and contracts between callers and callees, and context from other files/services in a 'readable on the spot' format. Do not modify the code itself (for implementation changes, use implement-issue). Refer to code-comment-style for detailed rules, create-commit for commit creation, and update-docs for CLAUDE.md synchronization.
Bootstrap a Bun workspaces monorepo — Elysia API (one file per route group), Vite/React/Tailwind v4 web with coss UI as the base component library and lucide-react icons, Drizzle/Postgres db package, per-workspace zod-validated config/env.ts, shared zod schemas validated at both ends, shared pino logger with request correlation, Better Auth, centralized useRoutes.ts, React context-module vs hook conventions, SPA SEO via Cloudflare Worker + API share.html, bun:test, mandatory code-comment spec (file headers, doc comments, TODO/ASSUMPTION/CONFIRM tags), ESLint flat + Prettier, one-command `bun run check`, dev.sh multi-port stack, Conductor settings.toml. Use when asked to scaffold/start a new Bun monorepo, add a workspace/route/context to one, fix SPA social cards, or set up this stack.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Rewrite AI-generated developer text to sound human — fix inflated language, filler, tautological docs, and robotic tone. Use after review-ai-writing identifies issues.
In-code documentation, folder READMEs, and code comments. Use when writing README.md files, JSDoc comments, or explaining code organization.
Comprehensive patterns and techniques for removing AI-generated verbosity and slop
표준 한국어 규칙에 기반한 문법, 맞춤법, 띄어쓰기, 구두점 검사기. 맞춤법 오류(되/돼, -ㄴ지/-는지), 띄어쓰기 오류(의존명사, 보조용언), 문법 오류(조사 사용, 시제), 구두점 문제를 감지하고 교정합니다. 다음 상황에 사용하세요. (1) 한국어 문서 작성 후 검토 (2) 작성 중 실시간 교정 (3) 코드의 한국어 주석이나 문서 검사 (4) 설명과 함께 한국어 문법 학습 (5) 공식 문서 품질 보장
General Correctness rules, Rust patterns, comments, avoiding over-engineering. When writing code always take these into account
Use when documenting public APIs. Use when writing library code. Use when using JSDoc-style comments. Use when generating documentation. Use when explaining complex types.
Trim and freshen technical documents, READMEs, design notes, PR descriptions, internal messages, and source-code comments or docstrings. Uses independent fresh-reader reviews to expose author-context bias, then deletes repetition, defensive caveats, filler, decorative structure, and code restatements while preserving facts, decisions, actions, constraints, and necessary rationale. Use when text is overexplained, repetitive, hard to scan, written while thinking, or when comments restate code or have drifted out of sync with it.
HTML structure, data attributes, and commenting guidelines for Shopify themes. Use when structuring HTML markup and adding comments to Shopify theme code.
Use this skill BEFORE writing or editing any Go (.go) files. Triggers when about to create, modify, or add code to .go files. Enforces happy path coding, error wrapping, sentinel errors, and godoc-style comments.