Loading...
Loading...
Found 885 Skills
Explain blockchain fundamentals including distributed ledger architecture, consensus mechanisms, and block structure. Use this skill when the user needs to understand blockchain concepts, evaluate whether blockchain fits a use case, or design a blockchain-based solution — even if they say 'how does blockchain work', 'do I need blockchain', or 'distributed ledger'.
Optional Stage 0 of the feature workflow — clarify vague ideas through dialogue until they are ready to enter the design phase. The role of AI is a thinking partner: dig out the real problem the user wants to solve (instead of sticking to the first solution they blurt out), actively evaluate the solution when the user brings it up, and propose better alternatives if necessary. After the discussion, output {slug}-brainstorm.md to document the results. Trigger scenarios: The user says "I have an unclear idea", "Let's brainstorm first", "The feature direction is still undecided", or the user brings a specific solution but wants to hear other ideas first. Skip this stage and proceed directly to design if the idea is already clear and the user does not want to discuss the solution further. This stage also does not handle bugs and refactoring.
Two-way sync between a local paper directory and an Overleaf project via the Overleaf Git bridge (Premium feature). Lets you keep ARIS audit/edit workflows on the local copy while collaborators edit in the Overleaf web UI. Token never touches the agent — user does the one-time auth via macOS Keychain. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to bridge their ARIS paper directory with an Overleaf project.
Skill Index and Orchestration Center — Automatically routes to the correct skill combination and orchestrates execution order based on user intent. Triggered when users ask questions involving stock quotes, cryptocurrencies, technical indicators, financial news, research report generation, or any scenario that requires skill invocation. Also triggered when users ask "Where does the data come from?", "What can you do?", or "What features do you have?"
Onboard a new repository or a repository with scattered documents into the CodeStable system. Two paths are automatically determined: the empty repository path (no spec-type documents or codestable/ directory in the repository) builds the skeleton from scratch; the migration path (the repository already has scattered documents or partial codestable/ structure) first generates an audit report + migration mapping plan, which is finalized after user confirmation one by one. This skill only does two things: "build the skeleton" and "organize existing documents". Once the skeleton is built, all sub-workflows can run directly. Trigger scenarios: Users say "Use CodeStable in this project", "Build CodeStable structure", "Initialize CodeStable", "Migrate to CodeStable".
Meta-skill: research a thinker's framework deeply, then synthesize a new Claude Code skill that applies their thinking to business ideas. Takes a prompt like "/add-thinker Andy Grove — Only the Paranoid Survive" and produces a new skill at .claude/skills/<thinker>/SKILL.md that works like /munger does. Use when the user says "add thinker", "add a new thinker", "codify X's thinking", or "make a skill for <person>'s framework".
Search and interpret bitdrift documentation for product behavior, SDK setup, API and service docs, and best practices. Use whenever the user asks how bitdrift works, how to set up the SDK, how to configure a feature, what an API or service does, or for conceptual guidance about bitdrift — even if they do not explicitly mention documentation. Also trigger when the user mentions /bd-docs or asks about bitdrift concepts, architecture, or integration guides.
Build and configure a GraphQL API backed by Neo4j using @neo4j/graphql v7 (current) or v5 (LTS). Covers Neo4jGraphQL constructor, getSchema(), assertIndexesAndConstraints(), type definitions with @node, @relationship (IN/OUT/UNDIRECTED), @cypher for custom resolvers, @authorization/@authentication for JWT/JWKS security, auto-generated queries/mutations, OGM programmatic access, subscriptions via CDC, and Apollo Federation. Use when writing typeDefs, securing fields, or wiring Neo4j to Apollo Server. Does NOT handle raw Cypher outside resolvers — use neo4j-cypher-skill. Does NOT cover Spring Data Neo4j entity mapping — use neo4j-spring-data-skill.
End-to-end testing patterns with Playwright for full-stack Python/React applications. Use when writing E2E tests for complete user workflows (login, CRUD, navigation), critical path regression tests, or cross-browser validation. Covers test structure, page object model, selector strategy (data-testid > role > label), wait strategies, auth state reuse, test data management, and CI integration. Does NOT cover unit tests or component tests (use pytest-patterns or react-testing-patterns).
Use when creating, modifying, or removing API endpoints on a Datex Studio branch. Covers the full lifecycle: requirements, prerequisite creation (datasources, flows), endpoint wiring, and verification. Trigger for: "create an endpoint", "expose this flow as an API", "add an API for X", "modify endpoint", "remove endpoint", "change endpoint alias", "create an API that does X".
Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when you need someone to find the holes before the board does, make a decision you've been avoiding, or understand what actually went wrong.
Adversarial reading methodology for narrative fiction — find what doesn't work, not confirm what does. Focus-area driven with dedicated resources per area. Use when reviewing drafts, evaluating prose quality, or assessing changes at any stage.