agents-md-writer
No SKILL.md available for this skill.
View on GitHubMore from sjunepark/custom-skills
architecture-md-writer
Create, update, review, and split ARCHITECTURE.md files that explain a codebase's shape, major components, runtime flow, code map, and important invariants. Use when a repository lacks architecture docs, an existing ARCHITECTURE.md is stale or too detailed, a subsystem needs its own nested ARCHITECTURE.md, or a root architecture doc should link to deeper module architecture docs.
27briefing
Manually brief the user on the current task or session so they can make the next decision without reloading the whole codebase. Use only when the user explicitly asks for a briefing, catch-up, current state, relevant architecture, or implementation context. Prefer this skill for task-scoped context recovery when the conversation is long, the code has changed, or the user wants the relevant details without a long explanation.
22tailwind-semantic-theme
Set up or refactor Tailwind v4 app theming around shadcn-compatible semantic CSS tokens without using shadcn itself. Use only when the user explicitly asks for this skill by name or explicitly asks for this exact methodology: OKLCH theme variables in `:root` and `.dark`, class-based dark mode, `@theme inline`, and shadcn-compatible token naming for future UI compatibility.
21teach
Teach the user how code, a subsystem, or a relevant technical concept works in clear learning order, with embedded snippets and ASCII diagrams when they materially improve understanding. Use whenever the user asks to be taught a part of the current codebase, a feature flow, an architecture area, a module, an API boundary, a data flow, or a relevant library or framework concept needed to understand the code. Prefer this skill when the user wants explanation, understanding, or guided learning rather than implementation, and when they want snippets instead of file or line references. If the request is specifically about what changed in a diff, commit, or patch, prefer `change-explainer`.
19change-explainer
Teach a code or document change set in clear learning order, with embedded snippets, before/after contrasts, and clear implications. Use whenever the user wants help understanding a `git diff`, unstaged changes, a commit, commit range, PR patch, or two versions of a file or document, especially when they want a guided walkthrough that starts with the big picture and then explains why and how the patch works. Prefer this skill when the user wants snippets instead of file or line references, even if they only ask "walk me through this diff" or "help me understand these changes.
19structure-review
Review code structure for both unnecessary complexity and insufficient organization. Use whenever the user asks whether code is overengineered, too abstract, too flat, poorly organized, too configurable, too future-proof, whether extra DB columns/fields/helpers should exist, whether a change feels heavier than necessary, whether modules or directories mix unrelated responsibilities, or wants help simplifying or reorganizing code while keeping readability benefits such as clear names, small object boundaries, or helpful file structure.
13