content-strategy
Build and execute a content marketing strategy for a solopreneur business. Use when planning what content to create, deciding on content formats and channels, building a content calendar, measuring content performance, or systematizing content production. Covers audience research for content, content pillars, distribution strategy, repurposing workflows, and metrics. Trigger on "content strategy", "content marketing", "what content should I create", "content plan", "content calendar", "content ideas", "content distribution", "grow through content".
go-to-market
Build a go-to-market (GTM) strategy for launching a product or entering a new market. Use when planning how to reach customers, position your product, choose channels, set pricing, and execute launch. Covers market entry strategy, customer segmentation, positioning, channel strategy, and GTM execution plan. Trigger on "go-to-market", "GTM strategy", "market entry", "launch strategy", "how to reach customers", "GTM plan".
copywriting
Write persuasive copy for landing pages, emails, ads, sales pages, and marketing materials. Use when you need to write headlines, CTAs, product descriptions, ad copy, email sequences, or any text meant to drive action. Covers copywriting formulas (AIDA, PAS, FAB), headline writing, emotional triggers, objection handling in copy, and A/B testing. Trigger on "write copy", "copywriting", "landing page copy", "headline", "write a sales page", "ad copy", "email copy", "persuasive writing", "how to write [marketing text]".
paid-advertising
Plan, launch, and optimize paid advertising campaigns for a solopreneur business. Use when running ads on Google, Facebook, LinkedIn, or other platforms to drive traffic, leads, or sales. Covers platform selection, campaign structure, ad copy and creative, targeting, budget allocation, conversion tracking, and optimization based on performance data. Trigger on "paid ads", "run ads", "Facebook ads", "Google ads", "advertising strategy", "ad campaign", "PPC", "how to advertise".
closing-deals
Close sales deals consistently as a solopreneur. Use when a prospect is at the decision stage and you need to move them to yes, when deals are stalling or going cold, when you need closing scripts or techniques, or when you want to build a repeatable process for turning proposals into signed contracts. Covers decision-stage psychology, closing techniques, stall recovery, contract-to-payment flow, and post-close relationship setup. Trigger on "how do I close a deal", "closing deals", "deal stalling", "prospect not responding", "how to get them to say yes", "close the sale", "convert proposal to client", "sales closing".
email-marketing
Build and execute email marketing campaigns for a solopreneur business. Use when building an email list, writing email sequences (welcome, nurture, sales), designing broadcast campaigns, improving open and click rates, or setting up email automation. Covers list building, segmentation, email copywriting, sequence design, deliverability, and metrics. Trigger on "email marketing", "email campaign", "email sequence", "email list", "newsletter", "email automation", "improve email open rates", "nurture emails", "welcome email".
customer-retention
Build and execute customer retention strategies for a solopreneur business. Use when reducing churn, improving customer lifetime value, building loyalty programs, re-engaging inactive users, or creating retention-focused product and communication strategies. Covers churn analysis, retention cohorts, lifecycle marketing, win-back campaigns, and loyalty mechanics. Trigger on "customer retention", "reduce churn", "keep customers", "improve retention", "churn rate", "customer loyalty", "win-back campaign".
negotiation
Navigate negotiations as a solopreneur — pricing, scope, terms, and contracts. Use when a prospect pushes back on price, wants to change scope, disputes terms, or when you need to structure a deal that works for both sides. Covers negotiation psychology, common objection responses, BATNA (Best Alternative To a Negotiated Agreement), anchoring, and solopreneur-specific scenarios like rate negotiations and contract terms. Trigger on "negotiate", "negotiation", "they want a discount", "price pushback", "contract negotiation", "how to negotiate", "client wants lower price", "negotiate terms".
outreach-and-prospecting
Run cold and warm outreach campaigns to find and engage potential customers or partners. Use when building a prospecting pipeline, writing cold emails or LinkedIn messages, identifying and qualifying leads, planning an outreach strategy, or scaling lead generation as a solopreneur. Covers lead identification, qualification frameworks, cold email writing, LinkedIn outreach, multi-touch sequences, and tracking. Trigger on "cold outreach", "prospecting", "find customers", "cold email", "LinkedIn outreach", "lead generation", "outreach strategy", "build a pipeline", "find clients".
bookkeeping-basics
Set up and maintain basic bookkeeping for a solopreneur business. Use when tracking income and expenses, preparing for taxes, managing invoices and receipts, understanding cash flow, or generating financial reports. Covers accounting software selection, chart of accounts, expense categorization, reconciliation, and financial statements. Not professional accounting advice — consult a CPA for complex situations. Trigger on "bookkeeping", "accounting", "track expenses", "financial records", "QuickBooks", "invoicing", "receipts", "profit and loss".
legal-essentials
Understand and handle essential legal matters for a solopreneur business. Use when forming a business entity, protecting intellectual property, writing contracts, understanding liability, or navigating basic legal requirements. Covers business structure selection, contracts and terms of service, IP protection basics, and when to hire a lawyer. Not legal advice — consult a lawyer for specific situations. Trigger on "legal", "business entity", "LLC", "contracts", "terms of service", "intellectual property", "liability", "legal protection".
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
cloudflare-workers
Build stateful serverless applications using Cloudflare Workers and Durable Objects. Use when creating real-time collaborative apps, chat systems, multiplayer games, WebSocket servers, rate limiters, or any application requiring coordination between clients, persistent state, or scheduled tasks with Cloudflare's edge computing platform.
ai-sdk-v6
Guide for building AI-powered applications using the Vercel AI SDK v6. Use when developing with generateText, streamText, useChat, tool calling, agents, structured output generation, MCP integration, or any LLM-powered features in TypeScript/JavaScript applications. Covers React, Next.js, Vue, Svelte, and Node.js implementations.
dotnet-best-practices
Comprehensive .NET development guidelines covering error handling, async patterns, type design, database performance, API design, DI, architecture, serialization, performance optimization, logging, and testing. Contains 100+ rules prioritized by impact to guide code reviews and automated refactoring.
side-effect-isolation
Enforce side-effect isolation: identify side effects, move them to boundary adapters/effects, keep Domain pure, and keep UI declarative with signals.
workspace-context
Workspace context patterns for src/app/workspace, including workspace lifecycle, stable context signals, workspace switching, and event emission for other modules; use when changing workspace selection, hydration, or context providers.
shell-ui
Shell module patterns for src/app/shell, covering global UI state, layout composition, navigation, theming with Material Design 3 tokens, and zone-less signal-first presentation boundaries; use when changing app chrome or global UI concerns.
change-management
Keep interfaces stable and changes reviewable; includes ADR-lite guidance and deprecation/deletion checks.
core-design-principles
Apply Black-Tortoise design principles (Occam, cohesion/coupling, tool-first assembly, explicit boundaries, deletion-friendly evolution) to a concrete change request; use as a pre-flight checklist before writing code.
d3-visualization
D3 ecosystem guidance for designing and implementing interactive charts/diagrams in Angular (signals-first, accessible, performant).
dependency-supply-chain
Change discipline for adding/upgrading dependencies; keeps diffs small, avoids unnecessary packages, and preserves deletion-friendly architecture.
design-for-deletion
Apply 'design for deletion' to a change: define the deletion path, avoid cross-context entanglement, and keep shared additions minimal and enduring.
tool-first-assembly
Apply Tool-First, Then Assembly during implementation: extract the smallest reusable tool(s) first, then wire them via assembly in outer layers without increasing coupling.
account-identity
Identity and account patterns for src/app/account, including AngularFire Auth integration, signal-first auth state, route guards, and security boundaries; use when touching auth, user/session state, or account UI flows.
angular-ecosystem
Useful Angular libraries, tools, and ecosystem references for Angular development.
angular-fire
Best practices and code patterns for @angular/fire version 20+, integrating Firestore and Auth with Signals and DDD architecture.
angular-material-cdk-animations
Angular Material + CDK + @angular/animations usage patterns aligned with zoneless + signals-first UI and M3 tokens.
architecture-ddd
Domain-Driven Design patterns, concepts, and guidance for software architecture.
capabilitys-layer
Patterns for implementing features under src/app/capabilitys, including presentation/application/domain/integration boundaries, NgRx Signals stores, event-driven communication, and Angular 20 template rules; use when adding or changing a capability.
mcp-codacy
Use the Codacy MCP server (@codacy/codacy-mcp) to run static analysis, retrieve findings, and focus remediation on high-signal issues; use when you need code quality feedback aligned with repo gates (lint, build, architecture:gate).
centralized-state-distributed-behavior
Apply centralized state + distributed behavior to a change: choose the single source of truth, keep writes through explicit commands, and place behavior in the correct owning layer.
cohesion-coupling-review
Review a proposed change for high cohesion/low coupling; recommends the smallest boundary-safe refactor (ownership, minimal public surface, no reach-in imports).
shared-kernel
Shared kernel rules for src/app/shared, defining what can be shared safely (primitives, utilities, UI atoms) and what must not (business logic, cross-context policies); use when adding shared helpers or components.
security-privacy
Pre-flight security & privacy checklist for changes touching identity, data, logging, or external integrations; ensures secrets/PII hygiene and boundary-safe design.
signals-first
Enforce 'Signals first, streams when needed' in a change: keep UI state as signals, isolate streams to boundaries, and convert Observables at the Application/facade boundary.
quality-gates
Auditing, testing, and architecture-governance instructions for Black-Tortoise, covering when to run `architecture:gate`, update docs/AUDIT-*, ship tests, and satisfy `.github/instructions/64-quality-testing-copilot-instructions.md` before merge.
single-responsibility
Apply SRP to a change request: identify mixed responsibilities, propose the smallest split, and keep interfaces minimal (paired with Occam/tool-first).
material-design-3
Material Design 3 (Material You) design system knowledge for modern web and Angular applications. Use when implementing Material Design 3 theming, components, typography, color systems, dynamic color, accessibility patterns, or migrating from Material Design 2. Covers design tokens, theming APIs, and Material You principles.
integration-layer
Infrastructure and integration patterns for src/app/integration, including Firebase/AngularFire usage, Data Connect codegen, repository adapters, DTO mapping, and streaming boundaries; use when touching persistence, external APIs, or platform SDKs.
firebase-platform
Firebase services, platform guides, and tips for integration with Angular projects.
explicit-boundaries
Enforce explicit boundaries in a change: place code in the right layer, keep capability isolation, use ports/adapters and events, and align with architecture gate rules.
evolution-maintainability
Apply evolution & maintainability principles to a change: keep interfaces minimal, improve ownership/naming, prefer deletion-friendly refactors, and align with quality gates.
eventing-hub
Event-sourcing and EventBus directives for Black-Tortoise, covering structured event schemas, append-before-publish flow, causality/id rules, and safe subscribers; use when touching src/app/eventing, EventBus, or any event handlers/projections.
e2e-playwright
Best practices for E2E testing with Playwright, focusing on Angular 20, Firebase Emulators, and Architecture Guards.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
unidirectional-data-flow
Enforce unidirectional data flow in a change: define explicit commands, keep writes in Application, expose state via signals, and isolate side effects at boundaries.
vscode-ext-commands
Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices
mcp-sequential-thinking
Use the sequential thinking MCP server (@modelcontextprotocol/server-sequential-thinking) to break down complex problems into ordered, testable steps; use when the task requires careful multi-step reasoning, risk reduction, or dependency-sensitive refactors.
Page 1244 of 1251 · 62526 results
