Frontend builder stack
A curated sequence for planning, designing, implementing, testing, and deploying product interfaces.
- Workflow stages
- 6
- Curation
- Editorial
- Reviewed
- 2026-07-30
How to use this collection
The collection shows a suggested sequence and responsibility for each Skill. Do not install everything by default; start with the stage that matches a real workflow gap.
- 01Stage 1
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
Quality 100/1000 platforms0 risk flags - 02Stage 2
design-analysis
Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "
Quality 100/1001 platforms0 risk flags - 03Stage 3
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance
Quality 100/1000 platforms0 risk flags - 04Stage 4
agents-hooks
Configures Claude Code hooks and Codex hooks.json/notify callbacks. Use when adding guardrails, preflight, audit trails, worktree automation, or budget enforcement.
Quality 99/1002 platforms1 risk flags - 05Stage 5
c-audit
Audit C code for security, safety, and memory management. Use when reviewing or hardening C modules.
Quality 99/1000 platforms0 risk flags - 06Stage 6
cache-dit-model-integration
High-level guide for integrating a new DiT model into cache-dit: Cache (BlockAdapter/ForwardPattern), Context Parallelism, Tensor Parallelism, Text Encoder Parallelism (TE-P), VAE Parallelism (VAE-P), generate CLI, installation, testing workflow, and detailed references. Use when adding support for a new diffusion transformer model in cache-dit.
Quality 99/1000 platforms1 risk flags
Collection completion rule
A workflow is complete when the target outcome is met with acceptable permissions and maintenance—not when every listed Skill is installed.
Build a private local stack