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.
Skills
vinkydev/vibestart
Compose a full-stack TypeScript stack and get a cutting-edge, verified project made for AI coding agents, with type safety, lint, and tests built in. | 自由组合全栈 TypeScript 技术栈,得到一个前沿、经过验证、为 AI 编码智能体打造的项目,内置类型安全、lint 与测试。
npx skilld add vinkydev/vibestart --allBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Use when writing a PR body.
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.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.
Move the pinned dependencies to their latest targets, verify, and open a pull request.
Use the vibestart CLI to create a TypeScript project, choose a stack or recipe, add capabilities such as Knip, Ultracite or Docker, diagnose project state, or upgrade templates while preserving business edits, including resolving conflicts and porting template changes to starter source. Use when the user mentions vibestart, asks to maintain a project with a vibestart.jsonc, or needs help with these CLI workflows. Not for ordinary application feature development unrelated to the CLI.
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Curated skills from @vinkydev. Checked GitHub just now