Loading...
Loading...
Found 1,655 Skills
Draft or update requirement documents under `codestable/requirements/` for the project — use **user stories + plain language** to describe a capability's "reason for existence, solution approach, and boundaries", so non-technical readers can quickly understand the highlights of the system. Layered with architecture: requirement is the "problem space" (why this capability is needed), while architecture is the "solution space" (what structure is used to implement it). Two modes: new (draft a new requirement doc from scratch), update (refresh an existing doc based on new materials or implementation changes). Single-target rule — only modify one document at a time. Trigger scenarios: the user says "fill in a requirement doc", "write down the requirements for this capability", "update the requirements directory", or during the feature-design phase, it is found that there is no corresponding requirement for the capability to be implemented this time.
Analyzes code architecture and structure — layer violations, circular dependencies, god objects, anemic domain models, missing boundaries, directory structure issues, and configuration problems. Generates severity-scored findings with fix prompts. Trigger phrases: "architecture review", "structure check", "layer analysis", "god class".
Use when working with Obsidian vaults, markdown notes with [[wikilinks]], ![[embeds]], callouts (> [!type]), YAML frontmatter/properties, #tags, block IDs (^id), ==highlights==, %%comments%%, Obsidian CLI commands (obsidian create/read/append/search/move/tags/daily/etc.), vault organization (PARA, MOC, flat+tags, Johnny Decimal), folder restructuring, daily notes, templates, task management, backlink analysis, or any file operations in an Obsidian vault directory. Trigger this skill whenever the user mentions Obsidian, .md files inside an Obsidian vault, knowledge base organization, or note-taking workflows — even if they don't explicitly say "Obsidian".
Qualtrics XM platform help — CX surveys (NPS/CSAT/CES), Employee Experience (EX) pulse surveys, Strategy & Research, Experience Agents AI, XM Directory, dashboards, REST API v3, MCP servers. Use when surveys aren't getting responses, dashboards won't show the right data, API calls return errors, you're setting up Qualtrics for the first time, confused by XM Directory contact management, need to export response data, comparing Qualtrics vs Medallia, or Qualtrics is too complex and you need guidance. Do NOT use for general NPS/CSAT strategy across tools (use /sales-customer-feedback) or product review collection like Trustpilot or G2 (use /sales-customer-reviews).
LaunchVibe platform help — product launch and discovery directory for makers, founders, and creators with daily launches, community upvoting/commenting, and XP gamification system. DR10 dofollow backlinks, free submission, no editorial queue. Covers submission process, listing optimization, XP and streak system, community engagement strategy, and daily launch timing. Use when your LaunchVibe listing isn't getting upvotes, not sure how to stand out on launch day, or wondering if LaunchVibe is worth it for visibility. Do NOT use for multi-directory launch strategy (use /sales-launch-directory). Do NOT use for Product Hunt launches (use /sales-producthunt).
ProductBurst platform help — product launch and discovery platform for startups with daily and weekly rankings. Covers product submission (launch in under 5 minutes, no gatekeepers), daily/weekly leaderboard rankings (not single-day like Product Hunt), community upvoting, Top of Day/Week badges (shareable SVGs), featured homepage placement (one-time fee), do-follow backlinks (DR46), comment threads, idea validation without a full build, and marketplace. Use when your product isn't getting noticed on launch day, your ProductBurst listing isn't ranking, you need visibility without Product Hunt's gatekeeping, or you want a do-follow backlink from a DR46 directory. Do NOT use for general launch strategy across multiple directories (use /sales-launch-directory), email marketing (use /sales-email-marketing), or audience growth (use /sales-audience-growth).
Develop custom React + Vite webapps in Steedos packages (webapps/ directory). Build custom amis Renderer components via IIFE compilation, with JSX runtime shimming (amisRequire), CSS scope isolation (postcss-prefix-selector), ScopedContext registration, Express router for SPA access, Tailwind v4 workarounds, and multi-webapp management. Covers vite.amis.config.ts, amis-entry.ts, amis-jsx-shim.ts, client loader files (main/default/client/*.client.js with waitForThing/loadJs/loadCss), build scripts, and deployment to public/.
Initialize the memory system in the current directory, generating CLAUDE.md (optional AGENT.md for Cursor), MEMORY.md, and the memory/ directory. Triggered when the user says "initialize memory", "set up memory", "memory init", or "/memory-init".
Use when designing or architecting Elixir/Phoenix applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models with Ash Framework, structuring multi-app projects with path-based dependencies, or preparing handoff documentation for Director/Implementor AI collaboration
Generate cinematic videos with native synchronized audio using ByteDance Seedance 2.0 (Fast) via EachLabs. Supports text-to-video (bytedance-seedance-2-0-text-to-video-fast) and image-to-video (bytedance-seedance-2-0-image-to-video-fast). Use when the user specifically asks for Seedance 2.0, wants native audio with the video, realistic physics, director-level camera control, or 4–15 second clips up to 720p.
Work with any Upstash TypeScript/JavaScript SDK including Redis, Box, QStash, Workflow, Vector, Search and Ratelimit. Use when the user is working with any Upstash product or SDK.
Audit and automatically optimize a lovstudio skill against repo conventions and official Anthropic skill-creator best practices, then bump the semver version and append a CHANGELOG entry. Checks SKILL.md frontmatter/trigger quality, script CLI hygiene, directory naming, README badge, and progressive disclosure structure. Prioritizes issues raised in the current conversation (e.g. bugs the user just hit) over a generic sweep. Use when the user asks to "optimize", "refine", "audit", or "polish" an existing skill, or when they say "bump version", "update changelog", or "fix this skill". Also trigger when the user mentions "优化 skill", "skill 审计", "刷一遍 skill", "skill-optimizer", "bump skill version", "update skill changelog".