code-data-analysis-scaffolds
Generates structured scaffolds (frameworks, checklists, templates) for technical work — TDD test suites, exploratory data analysis plans, statistical analysis designs, causal vs predictive modeling objectives, and validation checklists. Use when starting technical work that needs systematic planning before execution. Invoke when user mentions "write tests for", "explore this dataset", "analyze", "model", "validate", "design an A/B test", or when technical work needs scaffolding before execution.
What this skill does
# Code Data Analysis Scaffolds
## Table of Contents
- [Overview](#overview)
- [Workflow](#workflow)
- [Scaffold Types](#scaffold-types)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)
## Overview
This skill provides structured scaffolds for common technical patterns:
1. **TDD Scaffold**: Given requirements, generate test structure before implementing code
2. **EDA Scaffold**: Given dataset, create systematic exploration plan
3. **Statistical Analysis Scaffold**: Given question, design appropriate statistical test/model
4. **Validation Scaffold**: Given code/model/data, create comprehensive validation checklist
**Skip this skill** when the user wants immediate execution without scaffolding, already has a clear plan, or the task is trivial.
**Quick example:**
> **Task**: "Write authentication function"
>
> **TDD Scaffold**:
> ```python
> # Test structure (write these FIRST)
> def test_valid_credentials():
> assert authenticate("[email protected]", "correct_pass") == True
>
> def test_invalid_password():
> assert authenticate("[email protected]", "wrong_pass") == False
>
> def test_nonexistent_user():
> assert authenticate("[email protected]", "any_pass") == False
>
> def test_empty_credentials():
> with pytest.raises(ValueError):
> authenticate("", "")
>
> # Now implement authenticate() to make tests pass
> ```
## Workflow
Copy this checklist and track your progress:
```
Code Data Analysis Scaffolds Progress:
- [ ] Step 1: Clarify task and objectives
- [ ] Step 2: Choose appropriate scaffold type
- [ ] Step 3: Generate scaffold structure
- [ ] Step 4: Validate scaffold completeness
- [ ] Step 5: Deliver scaffold and guide execution
```
**Step 1: Clarify task and objectives**
Ask user for the task, dataset/codebase context, constraints, and expected outcome. Determine if this is TDD (write tests first), EDA (explore data), statistical analysis (test hypothesis), or validation (check quality). See [resources/template.md](resources/template.md) for context questions.
**Step 2: Choose appropriate scaffold type**
Based on task, select scaffold: TDD (testing code), EDA (exploring data), Statistical Analysis (hypothesis testing, A/B tests), Causal Inference (estimating treatment effects), Predictive Modeling (building ML models), or Validation (checking quality). See [Scaffold Types](#scaffold-types) for guidance on choosing.
**Step 3: Generate scaffold structure**
Create systematic framework with clear steps, validation checkpoints, and expected outputs at each stage. For standard cases use [resources/template.md](resources/template.md); for advanced techniques see [resources/methodology.md](resources/methodology.md).
**Step 4: Validate scaffold completeness**
Check scaffold covers all requirements, includes validation steps, makes assumptions explicit, and provides clear success criteria. Self-assess using [resources/evaluators/rubric_code_data_analysis_scaffolds.json](resources/evaluators/rubric_code_data_analysis_scaffolds.json) - minimum score ≥3.5.
**Step 5: Deliver scaffold and guide execution**
Present scaffold with clear next steps. If user wants execution help, follow the scaffold systematically. If scaffold reveals gaps (missing data, unclear requirements), surface these before proceeding.
## Scaffold Types
### TDD (Test-Driven Development)
**When**: Writing new code, refactoring existing code, fixing bugs
**Output**: Test structure (test cases → implementation → refactor)
**Key Elements**: Test cases covering happy path, edge cases, error conditions, test data setup
### EDA (Exploratory Data Analysis)
**When**: New dataset, data quality questions, feature engineering
**Output**: Exploration plan (data overview → quality checks → univariate → bivariate → insights)
**Key Elements**: Data shape/types, missing values, distributions, outliers, correlations
### Statistical Analysis
**When**: Hypothesis testing, A/B testing, comparing groups
**Output**: Analysis design (question → hypothesis → test selection → assumptions → interpretation)
**Key Elements**: Null/alternative hypotheses, significance level, power analysis, assumption checks
### Causal Inference
**When**: Estimating treatment effects, understanding causation not just correlation
**Output**: Causal design (DAG → identification strategy → estimation → sensitivity analysis)
**Key Elements**: Confounders, treatment/control groups, identification assumptions, effect estimation
### Predictive Modeling
**When**: Building ML models, forecasting, classification/regression tasks
**Output**: Modeling pipeline (data prep → feature engineering → model selection → validation → evaluation)
**Key Elements**: Train/val/test split, baseline model, metrics selection, cross-validation, error analysis
### Validation
**When**: Checking data quality, code quality, model quality before deployment
**Output**: Validation checklist (assertions → edge cases → integration tests → monitoring)
**Key Elements**: Acceptance criteria, test coverage, error handling, boundary conditions
## Guardrails
- **Clarify before scaffolding** - Don't guess what user needs; ask clarifying questions first
- **Distinguish causal vs predictive** - Causal inference needs different methods than prediction (RCT/IV vs ML)
- **Make assumptions explicit** - Every scaffold has assumptions (data distribution, user behavior, system constraints)
- **Include validation steps** - Scaffold should include checkpoints to validate work at each stage
- **Provide examples** - Show what good looks like (sample test, sample EDA visualization, sample model evaluation)
- **Surface gaps early** - If scaffold reveals missing data/requirements, flag immediately
- **Avoid premature optimization** - Start with simple scaffold, add complexity only if needed
- **Follow best practices** - TDD: test first, EDA: start with data quality, Modeling: baseline before complex models
## Quick Reference
| Task Type | When to Use | Scaffold Resource |
|-----------|-------------|-------------------|
| **TDD** | Writing/refactoring code | [resources/template.md](resources/template.md) #tdd-scaffold |
| **EDA** | Exploring new dataset | [resources/template.md](resources/template.md) #eda-scaffold |
| **Statistical Analysis** | Hypothesis testing, A/B tests | [resources/template.md](resources/template.md) #statistical-analysis-scaffold |
| **Causal Inference** | Treatment effect estimation | [resources/methodology.md](resources/methodology.md) #causal-inference-methods |
| **Predictive Modeling** | ML model building | [resources/methodology.md](resources/methodology.md) #predictive-modeling-pipeline |
| **Validation** | Quality checks before shipping | [resources/template.md](resources/template.md) #validation-scaffold |
| **Examples** | See what good looks like | [resources/examples/](resources/examples/) |
| **Rubric** | Validate scaffold quality | [resources/evaluators/rubric_code_data_analysis_scaffolds.json](resources/evaluators/rubric_code_data_analysis_scaffolds.json) |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.