playing-to-win
Use when defining long-term product strategy, when needing to pivot from horizontal to vertical focus, or when teams struggle with prioritization due to serving too many use cases
Pre-Mortem Framework
Instead of waiting for a post-mortem after failure, imagine the project has already failed spectacularly and work backward to uncover hidden risks. Use before kicking off any major initiative, product launch, or high-stakes project.
pre-mortem-kill-criteria
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
Corporate Innovation C-Corp Model
To replicate startup speed in large companies, launch new products as separate legal entities (C-Corps) with distinct brands, reporting directly to the CEO, bypassing standard chains of command.
founder-prenup
Use before starting a company with co-founders, when bringing on a new co-founder, or annually as a relationship health check to prevent the 65% of startup failures caused by co-founder conflict
taste-driven-core
Use for core product areas defining long-term brand value, when A/B tests are fragmenting product vision, or when short-term optimization threatens architectural integrity
unstuck-scaling
Use when AI agents frequently hit dead ends, when reliability is the main constraint on scaling utility, or when general model improvements don't solve specific blockers
3-Month PMF Treadmill
Product-Market Fit is perishable in AI. LLM capabilities jump every 3 months, so you must pivot and reinvent your core value proposition quarterly. Accept high churn and throttle scaling for reinvention.
absolute-volume-framework
Use in power-law businesses like platforms or VC, when conversion rate optimization shrinks your funnel, or when efficiency metrics block potential outlier winners
Controllable Inputs Framework
Focus on Input Metrics (selection, price, speed) rather than Output Metrics (revenue, stock price). Inputs are controllable and causal; outputs are lagging. Amazon's flywheel philosophy.
Demand-Side Buying Timeline
A chronological model of the buying process from the customer's perspective—First Thought, Passive Looking, Active Looking, Deciding, First Use, Ongoing Use. Align sales to customer psychology, not your funnel.
gardening-mindset
Use when dealing with ecosystems, network effects, or high-uncertainty environments where the right answer cannot be known in advance, when rigid planning consumes more value than it creates
inner-scorecard
Use when deciding between a high-status opportunity and a riskier path that feels more aligned, when feeling trapped despite external success, or when auditing if your decisions serve your values or others' expectations
ai-teammate-model
Use when designing AI agent products, defining roadmaps for agentic workflows, or evaluating how to evolve AI from passive tool to proactive partner in software development
Builder Operating Model
Shift from rigid roles (PM, Designer, Engineer) towards a model where individuals use AI to bridge skill gaps, enabling smaller and flatter teams. Use in early-stage startups or innovation units where speed is critical.
nlx-design-stack
Use when designing AI agents or chatbots, when raw model outputs feel like a black box, or when building natural language interfaces that need structure and trust
three-layer-agent-stack
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
Dimensionality of Self-Management
View yourself as an entity with infinite dimensions rather than a single good/bad identity. Strengths and weaknesses are often the same trait in different contexts. Use during performance reviews or when receiving tough feedback.
Energy Audit and Zone of Genius
Review your calendar, color-code activities by energy impact (Green/Red), and systematically delegate draining tasks to maximize time in your Zone of Genius.
tavily-tools
>-
style-standards
Enforces style consistency for documentation and code with support for taxonomy, voice, and formatting domains. Use when creating or modifying files requiring: (1) markdown structure (headers, lists, tables, Dictums, separators), (2) code organization (comments, section dividers, naming conventions), (3) voice compliance (tone, grammar, imperative phrasing), or (4) formatting validation against project standards.
typescript-effect
>-
sonarcloud-tools
>-
parallel-dispatch
Orchestrates concurrent workstreams via Task tool for non-trivial requests. Decomposes complex tasks into 3-10 parallel agents with independent scopes and synthesizes results. Use when requests involve: (1) multiple investigative paths or validation layers, (2) research, analysis, or debugging exceeding trivial scope, (3) implementation planning requiring facet exploration, or (4) any moderate+ complexity task benefiting from parallel execution.
perplexity-tools
>-
command-builder
Creates and configures Claude Code slash commands with YAML frontmatter, argument handling, and tool permissions. Use when building new commands, adding $ARGUMENTS or $1-$N parameters, configuring allowed-tools, organizing command namespaces, or fixing command failures.
context7-tools
>-
deep-research
>-
plan-decompose
>-
skill-builder
Creates and edits Claude Code skills with YAML frontmatter, folder structure, and depth-scaled content. Use when building new skills, updating existing skills, designing SKILL.md metadata, organizing skill folders, validating skill structure, or adding Python and TypeScript scripts for deterministic operations.
design-synthesis
>-
exa-tools
>-
github-tools
>-
hooks-builder
>-
hostinger-tools
>-
mermaid-diagramming
>-
n8n-builder
>-
nx-tools
>-
output-style-builder
>-
agent-builder
Creates and configures Claude Code agent files (.claude/agents/*.md) with YAML frontmatter, tool permissions, model selection, and system prompt structure. Use when building new agents, configuring agent frontmatter, designing discovery triggers, setting tool permissions, writing system prompts, or selecting agent models.
moon
This skill should be used when the user asks to "configure moon", "set up moonrepo", "create moon tasks", "run moon commands", "configure moon workspace", "add moon project", "moon ci setup", "moon docker", "moon query", "migrate to moon v2", or mentions moon.yml, .moon/workspace.yml, .moon/toolchains.yml, moon run, moon ci, or moonrepo in general.
proto
This skill should be used when the user asks to "install proto", "configure proto", "manage tool versions", "pin versions", "set up .prototools", "install node version", "install rust version", "install python version", "proto plugins", or mentions proto commands, .prototools file, or multi-language version management.
bknd-storage-config
Use when configuring storage backends for file uploads. Covers S3-compatible storage (AWS S3, Cloudflare R2, DigitalOcean Spaces), Cloudinary media storage, local filesystem adapter for development, adapter configuration options, environment variables, and production storage setup.
bknd-setup-auth
Use when initializing or configuring the Bknd authentication system. Covers enabling auth, configuring password strategy, setting up JWT and cookie options, defining roles, and production security settings.
bknd-session-handling
Use when managing user sessions in a Bknd application. Covers JWT token lifecycle, session persistence, automatic renewal, checking auth state, invalidating sessions, and handling expiration.
bknd-troubleshoot
Use when encountering Bknd errors, getting error messages, something not working, or needing quick fixes. Covers error code reference, quick solutions, and common mistake patterns.
bknd-testing
Use when writing tests for Bknd applications, setting up test infrastructure, creating unit/integration tests, or testing API endpoints. Covers in-memory database setup, test helpers, mocking, and test patterns.
btca-bknd-repo-learn
Use btca (Better Context App) to efficiently query and learn from the bknd backend framework. Use when working with bknd for (1) Understanding data module and schema definitions, (2) Implementing authentication and authorization, (3) Setting up media file handling, (4) Configuring adapters (Node, Cloudflare, etc.), (5) Learning from bknd source code and examples, (6) Debugging bknd-specific issues
bknd-webhooks
Use when configuring webhook integrations in Bknd. Covers receiving incoming webhooks via HTTP triggers, sending outgoing webhooks with FetchTask, event-triggered webhooks on data changes, signature verification, retry patterns, and async processing.
bknd-client-setup
Use when setting up Bknd SDK in a frontend application. Covers Api class initialization, token storage, auth state handling, React integration with BkndBrowserApp and useApp hook, framework-specific setup (Vite, Next.js, standalone), and TypeScript type registration.
Page 1380 of 1713 · 85618 results
