composable-primitives

Included with Lifetime

$97 forever

Design composable agentic primitives for flexible workflows. Use when creating reusable workflow building blocks, designing SDLC primitives, or building agent operations that can be combined in different ways.

Design

What this skill does


# Composable Primitives Skill

Guide design of composable agentic primitives for flexible workflow creation.

## When to Use

- Designing new agentic workflows
- Customizing SDLC for specific needs
- Mapping problem classes to primitives
- Building organization-specific compositions

## The Secret

> "The secret of tactical agentic coding is that it's not about the software developer lifecycle at all. It's about composable agentic primitives you can use to solve any engineering problem class."

## Core Primitives

| Primitive | Purpose | Input | Output |
| --- | --- | --- | --- |
| **Classify** | Categorize input | Issue/task | Classification |
| **Plan** | Create implementation spec | Issue | Plan file |
| **Build** | Implement the plan | Plan file | Code changes |
| **Test** | Validate functionality | Code changes | Pass/fail |
| **Review** | Validate alignment | Spec + code | Issue list |
| **Patch** | Fix specific issues | Issue description | Targeted fix |
| **Document** | Generate documentation | Code changes | Doc files |
| **Ship** | Deploy to production | Validated code | Deployed state |
| **Branch** | Create isolated context | Classification | Branch name |
| **Commit** | Save checkpoint | Changes | Commit hash |

## Composition Workflow

### Step 1: Identify Problem Class

What type of work?

- Chore (simple, low risk)
- Bug (medium complexity, clear criteria)
- Feature (complex, full SDLC)
- Hotfix (urgent, minimal process)
- Documentation (content only)

### Step 2: Select Primitives

Based on problem class, choose primitives:

| Problem Class | Primitives |
| --- | --- |
| Chore | Classify -> Build -> Test -> Ship |
| Bug | Classify -> Plan -> Build -> Test -> Review -> Ship |
| Feature | Full SDLC |
| Hotfix | Patch -> Test -> Ship |
| Documentation | Document -> Review -> Ship |

### Step 3: Order by Dependencies

Ensure correct sequencing:

- Plan before Build (Build needs plan)
- Build before Test (Test needs code)
- Test before Ship (Ship needs validation)

### Step 4: Add Validation Points

Where should failures stop the pipeline?

```text
Plan -> Build -> [Test GATE] -> Review -> [Review GATE] -> Ship
```

### Step 5: Define Entry/Exit

- Entry: What triggers this workflow?
- Exit: What signals completion?

## Standard Compositions

### Full SDLC

```text
Classify -> Plan -> Build -> Test -> Review -> Document -> Ship
```

### ZTE (Zero-Touch)

```text
Classify -> Plan -> Build -> Test -> Review -> Document -> Ship
                              | |
                          [GATE]         [GATE]
```

### Quick Fix

```text
Classify -> Patch -> Test -> Ship
```

### Review-Driven

```text
Review -> Patch -> Test -> Ship
```

## Custom Composition Design

### Organization Factors

Consider:

- Testing requirements (mandatory E2E?)
- Review processes (who reviews?)
- Documentation standards (auto-generated?)
- Deployment pipelines (manual approval?)
- Compliance needs (audit trails?)

### Example: Compliance-Heavy

```text
Classify -> Plan -> [Compliance Review] -> Build -> Test ->
[Security Scan] -> Review -> Document -> [Approval] -> Ship
```

### Example: Rapid Iteration

```text
Build -> Test -> Ship (no planning for small changes)
```

## Key Memory References

- @composable-primitives.md - Detailed primitives documentation
- @template-engineering.md - Templates as primitive definitions
- @adw-anatomy.md - ADW as composition framework

## Output Format

Provide composition design:

```markdown
## Workflow Composition

**Problem Class:** {type}
**Entry Trigger:** {trigger}
**Exit Criteria:** {criteria}

### Primitives Selected
1. Classify - Categorize the task
2. Plan - Create implementation spec
3. Build - Implement changes
4. Test - Validate functionality
5. Ship - Deploy to production

### Composition Flow
```

Classify -> Plan -> Build -> Test -> Ship
                              |
                          [GATE: Must pass]

```markdown

### Validation Gates

- After Test: Abort if tests fail
- After Review: Optional based on confidence

### Customizations

- [Organization-specific additions]

```

## Anti-Patterns

- Rigid SDLC thinking (must do all steps)
- Over-composition (too many primitives)
- Under-composition (missing critical steps)
- Ignoring failure paths (no gates)
- One-size-fits-all (same for all problem classes)

## Version History

- **v1.0.0** (2025-12-26): Initial release

---

## Last Updated

**Date:** 2025-12-26
**Model:** claude-opus-4-5-20251101

Files: 1

Size: 4.7 KB

Complexity: 13/100

Category: Design

Source: https://github.com/melodic-software/claude-code-plugins/tree/main/plugins/tac/skills/composable-primitives

Related in Design

contribute

Included

Local-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".

Designscripts

architectural-analysis

Included

User-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).

Designscripts

mcp

Included

Model 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.

Designscripts

react-native-skia

Included

Design, 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.

Designscripts

plaid

Included

Product 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".

Designscripts

nextjs-framer-motion-animations

Included

Adds 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.

Designscripts