customer-onboarding
Design and execute customer onboarding that drives activation and retention. Use when building onboarding flows for new users, reducing churn in the first 30 days, improving time-to-value, or creating onboarding sequences (email, in-app, or manual). Covers activation metrics, onboarding step design, friction reduction, and measuring onboarding success. Trigger on "customer onboarding", "onboarding flow", "user onboarding", "reduce early churn", "improve activation", "onboarding sequence", "time to value".
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".
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".
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".
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.
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.
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.
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.
dependency-supply-chain
Change discipline for adding/upgrading dependencies; keeps diffs small, avoids unnecessary packages, and preserves deletion-friendly architecture.
workflows-orchestration
Workflow orchestration patterns for src/app/workflows, focusing on application-layer use cases, long-running flows, event-driven coordination, and deterministic state transitions; use when implementing multi-step user journeys or cross-capability processes.
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.
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.
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.
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.
security-privacy
Pre-flight security & privacy checklist for changes touching identity, data, logging, or external integrations; ensures secrets/PII hygiene and boundary-safe design.
d3-visualization
D3 ecosystem guidance for designing and implementing interactive charts/diagrams in Angular (signals-first, accessible, performant).
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.
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).
change-management
Keep interfaces stable and changes reviewable; includes ADR-lite guidance and deprecation/deletion checks.
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.
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.
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.
minimal-stable-interface
Apply MSI to a change: minimize exports, define ports/events at boundaries, and keep APIs intention-revealing and deletion-friendly.
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.
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.
architecture-ddd
Domain-Driven Design patterns, concepts, and guidance for software architecture.
angular-material-cdk-animations
Angular Material + CDK + @angular/animations usage patterns aligned with zoneless + signals-first UI and M3 tokens.
mcp-software-planning
Use the Software-planning-mcp MCP server (github:NightTrek/Software-planning-mcp) to generate requirements, designs, task breakdowns, and execution plans for changes in this repo; use when you need structured planning artifacts (requirements/design/tasks) before implementation.
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.
mcp-playwright
Use the Playwright MCP server (@playwright/mcp) for browser-driven verification, screenshots, console logs, and UI flow validation; use when debugging or validating Angular UI behavior beyond unit tests.
mcp-context7
Use the Context7 MCP server (@upstash/context7-mcp) to fetch authoritative, version-appropriate library documentation snippets (Angular, NgRx Signals, Firebase, RxJS, Playwright); use when you must confirm API usage, signatures, or best practices without relying on memory.
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).
angular-fire
Best practices and code patterns for @angular/fire version 20+, integrating Firestore and Auth with Signals and DDD architecture.
angular-ecosystem
Useful Angular libraries, tools, and ecosystem references for Angular development.
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.
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.
firebase-platform
Firebase services, platform guides, and tips for integration with Angular projects.
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.
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.
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
black-tortoise-ui-reviewer
Black-Tortoise UI review and fixes. Use when asked to review UI, layout, or design in this repo. Focus on Angular 20 + standalone components, Material Design 3 tokens, @ngrx/signals state, and DDD layer boundaries. Checks responsiveness, a11y, spacing, and M3 token usage; applies minimal fixes in presentation styles/templates.
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.
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.
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.
zig-expert
Comprehensive Zig 0.15.2 development expert. Use when writing Zig code, debugging memory issues, designing build systems, implementing comptime metaprogramming, handling errors, or cross-compiling. Automatically activated for any .zig file or build.zig work.
Page 1480 of 1487 · 74319 results
