Loading...
Loading...
Found 139 Skills
Use when beginning any design process - orchestrates gathering context, clarifying requirements, brainstorming solutions, and documenting validated designs to create implementation-ready design documents
Research codebase, write concrete implementation plan. Use after brainstorming.
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
Collaborative blog writing assistant that guides users from topic to structured draft through iterative brainstorming. Acts as an advanced rubber duck — asking tough questions to help authors think deeper and gain clarity. Use this skill when a user wants to write a blog post, structure their thoughts into a post, turn notes/context into a blog, or needs help organizing ideas for written content. Also trigger when users mention "blog", "write a post", "help me write about", or have context files they want to turn into publishable content. Do NOT use for: editing existing drafts, proofreading, formatting, or when user just wants you to write something for them without collaboration.
Guide developers through creating MCP apps. Covers the full lifecycle: brainstorming ideas against UX guidelines, bootstrapping projects, implementing tools/widgets, debugging, running dev servers, deploying and connecting apps to ChatGPT. Use when a user wants to create or update a MCP app, MCP server or use the Skybridge framework.
Invoke Codex as a coworker for implementation, brainstorming, specs, and reviews. Use when you want parallel thinking, cheap execution, or a second opinion. Codex tokens are cheaper than yours — delegate aggressively. Keywords: codex, delegate, implement, draft, review, brainstorm, write tests, code review, moonbridge.
Use this skill BEFORE implementing any new feature. This is NON-NEGOTIABLE for scope control. Use when evaluating features during brainstorming, planning new functionality, branches approach size limits (1000/1500/2000 lines, 15/25/30 commits). Do not use when feature is already approved and in progress. DO NOT use when: simple bug fixes with clear scope.
Use when starting a new project from scratch, before any technical decisions, to explore the idea through structured sessions and produce a brainstorming synthesis
Search Slack for interpreted organizational context -- decisions, constraints, and discussion arcs that shape the current task. Produces a research digest with cross-cutting analysis and research-value assessment, not raw message lists. Use when searching Slack for context during planning, brainstorming, or any task where organizational knowledge matters. Trigger phrases: 'search slack for', 'what did we discuss about', 'slack context for', 'organizational context about', 'what does the team think about', 'any slack discussions on'. Differs from slack:find-discussions which returns individual message results without synthesis.
Create structural blueprints for blog posts before writing. Analyzes topic briefs, selects structure templates, generates outlines with word counts and section summaries. Use when planning a new post, brainstorming structure, or deciding scope before drafting. Use for "outline", "plan post", "structure this topic", "how should I organize". Do NOT use for writing actual post content, editing existing posts, or SEO keyword planning.
Story brainstorming capture — minimal notes that preserve creative freedom. Use when exploring narrative ideas, discussing characters, planning chapters, or thinking through story possibilities. Supports interactive conversation and autonomous report mode for fan-out exploration.
Enables Claude to interact with Gemini AI chat for quick queries, brainstorming, and alternative AI perspectives