Loading...
Loading...
Found 642 Skills
Search through a personal material library with over 1800 real experiences and perspectives to add a human touch to content. Use this when users mention "personal experience", "real cases", "materials", or "human touch".
Interview the user relentlessly to expand context and surface intent, constraints, hidden assumptions, and unstated alternatives. Use whenever the user invokes `/grill-me`, says "grill me", "interview me", "pressure-test this", "help me think through", or whenever the user's first message is more decision than task — across coding, business, marketing, personal branding, SOPs, systems thinking, process design, and tough decisions.
A cross-cutting cognitive mode for sitting with design problems before rushing to solve them. Part of the Intent design strategy system. Activates expansive brainstorming: hyperassociativity, beginner's mind, cross-domain pattern recognition, and suppression of premature idea-dismissal. Works alongside every Intent skill — strategize uses it to reframe briefs, blueprint to question structural assumptions, journey to rethink interaction models, and specify to stress-test specs. Trigger when the user invokes "expansive mode", "philosopher mode", "sit with this", "brainstorm", "explore this problem", or says things like "go weird with it", "don't filter yourself", "what connections are you not making", "think about this differently", or "I'm stuck". This is a reasoning protocol, not a persona — Claude's voice stays grounded but the cognitive process changes significantly.
Use when designing character personalities, creating memorable motion signatures, ensuring animations feel polished, or making visual experiences that audiences want to watch.
Use when defining brand motion identity, creating animation guidelines for brand expression, or aligning animation with brand personality.
Novel Logic/Plot Review, applicable to user requests such as "Help me check if there are bugs in my novel", "Check if there are timeline contradictions", "Check if characters are OOC", "Find plot conflicts between different parts", "Sort out whether foreshadowings are resolved", "Check the rationality of novel plots", "Check if there are plot loopholes", "Character behaviors are inconsistent with their personalities", "Check if the timeline is correct", "Find contradictions in the novel", "Help me sort out all foreshadowings", "Novel plot bug check", "Logical loophole troubleshooting", etc. It detects issues such as timeline conflicts, logical loopholes, character OOC, and missing foreshadowings. **Performs word count checks to ensure chapter word counts meet standards**, **generates a detailed issue list and automatically fixes all issues, with the fixed results directly modifying the chapters/ directory and automatically backing up the original files to .sumeru/write/original/ before modification**, **uses sub-Agents for parallel processing during batch review, with each Agent responsible for a maximum of 3 chapters**
Pink Script — After Hours — Black canvas, hot pink accent, pearl-cream paper, Instrument Serif headlines: late-night editorial luxury. Anything that should feel nocturnal, intentional, and a little luxe: fashion brand decks, creator personal brands, after-hours / nightlife / spirits launches, luxury product reveals, editorial features.
Train custom AI models (LoRA) on fal.ai for personalized image generation tailored to a brand, character, or style.
Community stock lists (Sharelist) via Longbridge Securities — browse popular and personal lists, view list details and constituents, create/delete/manage your own lists, and add/remove symbols. Like a public watchlist that other users can subscribe to. Read operations require no login; write operations (create/delete/add/remove/sort) require login. Triggers: "股票清单", "公开清单", "热门清单", "社区选股", "选股清单", "股票列表", "清单管理", "股票清單", "公開清單", "熱門清單", "社區選股", "選股清單", "訂閱清單", "sharelist", "stock list", "public watchlist", "popular list", "community picks", "stock collection", "create list", "manage list", "subscribe list".
Build and maintain a persistent markdown wiki that an LLM updates on the user's behalf, usually inside an Obsidian vault or git-tracked notes repo. Use when raw sources such as web articles, papers, meeting notes, transcripts, screenshots, or past analyses need to be turned into an interlinked knowledge base with immutable source files, LLM-written wiki pages, `index.md`, `log.md`, schema rules in `AGENTS.md` or `CLAUDE.md`, source summaries, query notes, and recurring lint passes. Triggers on: llm-wiki, personal wiki, obsidian wiki, research vault, knowledge base, source ingest, persistent notes, wiki maintenance, source summaries, query filing.
Explain core Contentful concepts and route users to the right implementation skill or documentation. Use when users ask conceptual questions, need terminology clarified, want help choosing between APIs (CDA/CMA/CPA/GraphQL), or need guidance on the Contentful MCP server. Also triggers on "Contentful 101", "which Contentful API", "how do I get started", "which skill should I use", "what does X mean in Contentful", "Contentful glossary", "CDA vs CPA", "CDA vs GraphQL", "how does Contentful work", "Contentful architecture", "explain environments", "what are aliases", "content model design", "headless CMS", "Contentful MCP", "MCP server", "set up MCP", "Remix Contentful", "Astro Contentful", "Gatsby Contentful", "SvelteKit Contentful", "Nuxt Contentful". Not for framework-specific implementation (contentful-nextjs), migrations (contentful-migration), personalization (contentful-personalization), or hands-on REST/GraphQL request examples (contentful-api).
Plans real-user QA deliverables: personas, journey maps, exploratory charters, persona/journey/tour/CFR test cases, regression suites, Figma validation checks, automation intent, and user-impact bug reports. Writes artifacts under <qa-output-path>/qa/ for qa-execution to consume. Use when planning QA before execution, documenting journey-driven test strategy, marking flows that need E2E follow-up, or filing structured bug reports. Do not use for live execution, AI implementation audits, CI gate ownership, or technical integration/security/performance suites; use qa-execution or agent-output-audit instead.