Loading...
Loading...
Found 142 Skills
Clarify intent, propose 2-3 approaches, embedded grill to stress-test the chosen path. Use before any creative work — new features, components, behavior changes, design questions. Mockup-only requests use mockup quick-mode (no spec/plan ceremony).
Generates non-obvious ideas using Verbalized Sampling (VS-CoT). Use when the user needs to brainstorm novel solutions, avoid stereotypical patterns, or write creatively.
You MUST use this skill before any creative or complex work. Explores user intent, requirements and design before actually executing on the task.
Wide before deep. Fans out N parallel divergent thoughts under structurally different cognitive frames (regulator, biology, speedrunner, 10 year old, $0 budget), then scores, clusters, prunes traps, and deepens only the top survivors. The isolated parallel branches and the separated generator/critic phases are load-bearing. Do not collapse them into a single linear thought. Use when the user asks to brainstorm, ideate, generate options, design an architecture, name something, pick between approaches, plan a refactor, design an API or SDK surface, generate hypothesis classes for a fuzzy bug, or any prompt of the shape "give me a few ways to". Also use when the obvious answer feels obvious and wrong, or when the user explicitly invokes /adhd or asks for "ADHD mode".
Generate creative domain names and brand identifiers. Produces memorable, available domain suggestions with wordplay and semantic relevance.
Turns a jackin' roadmap item's intent into concrete design decisions through freeform discussion, written into its Design section. Use when the operator runs /jackin-dev:brainstorm.
Use this when users need help starting or continuing their writing (not diaries). Trigger scenarios include "don't know what to write", "help me brainstorm", "write a travelogue", "record TIL", "write something". For diary writing, please use the diary-assistant skill instead.
Use when exploring unclear requirements or architectural decisions - refines rough ideas into clear requirements/designs through collaborative questioning (one at a time), explores alternatives, validates incrementally. Activates when user has vague feature idea, mentions "not sure about", "exploring options", "what approach", or during spec-driven requirements/design phases.
Use when you need to turn a vague idea into a confirmed design spec before implementation (new feature/component/behavior change). First check project context, then ask one question at a time, provide 2-3 options with trade-offs, finally output design in segments (~200-300 words each) with confirmation after each. Triggers: brainstorm, clarify idea, design spec, refine concept, requirement clarification.
Use this skill when the user needs help with personal writing — either starting a new piece from scratch (inspiration/brainstorming) or reviewing and polishing an existing article (proofreading/editing). Invoke immediately when: the user shares an article and asks for feedback, wants to improve their writing style, feels stuck on what to write, wants help structuring a travel piece/TIL note/personal essay, or asks to review Chinese writing quality. Trigger phrases: 帮我改文章, 检查一下, 润色, 校对, 不知道写什么, 帮我构思, 写游记, 记录 TIL, 写点什么. NOT for diary writing (use diary-assistant) or formal business communications.
Generates genuinely novel, useful ideas for products, businesses, features, campaigns, names, research directions, and process redesign. Use when the user asks to brainstorm, ideate, improve a weak concept, escape generic answers, find differentiated options under real constraints, or turn a vague opportunity into a shortlist of strong concepts with wedges and tests. Preserves diversity with independent idea pools, analogy transfer, contradiction solving, critique-and-repair, and reality checks. Do not use for simple rewriting, proofreading, or purely factual research.
Use when thinking through ideas, investigating problems, or clarifying requirements — before or during a Beat change