pattern-dev

Codify pattern development workflows using the ./scripts/ct wrapper.

9|10|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/jkomoros/community-patterns --skill pattern-dev-jkomoros
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pattern-dev
Source: https://github.com/jkomoros/community-patterns/tree/main/.claude/skills/pattern-dev
Command: npx skills add https://github.com/jkomoros/community-patterns --skill pattern-dev-jkomoros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Day-to-day pattern development best practices. Use when actively developing patterns. Covers incremental development, commits, communication guidelines, and general development workflow.

Core Features & Use Cases

  • CT Commands: Use the ./scripts/ct wrapper: Always use the wrapper for ct commands to avoid directory churn and permission prompts.
  • Why the wrapper exists: Automatically handles directory changes, preserves path resolution, and enforces a no-prompts policy.
  • For detailed deployment commands: See the deployment skill for end-to-end guidance.
  • Framework Documentation: Quick access to labs framework docs to guide pattern development and debugging.
  • Incremental development & commits: Follow a pattern of small, verifiable commits to keep main stable.
  • Managing Dev Servers: Guidelines to restart dev servers when updating labs.
  • Debugging with <ct-cell-context>: Use as a targeted debugging aid to annotate values in context.

Quick Start

Use the CT wrapper to start a new development run: ./scripts/ct dev patterns/$GITHUB_USER/pattern.tsx --no-run

Frequently Asked Questions about pattern-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a predictable workflow for pattern development in labs?

Pattern development workflow codifies best practices for incremental development, commits, and deployment. Use the ./scripts/ct wrapper for all ct commands to avoid directory churn, preserve path resolution, and enforce a no-prompts policy. This ensures consistent, verifiable development cycles that keep main stable.

Why should I use the ct wrapper instead of running ct commands directly?

The ct wrapper automatically handles directory changes, preserves path resolution, and eliminates permission prompts—avoiding directory churn during development. It enforces a consistent no-prompts policy across your team, reducing friction and ensuring predictable command behavior.

What's the best way to structure commits during pattern development?

Follow small, verifiable commits to keep main stable and maintain development discipline. This incremental approach supports team communication guidelines and debugging practices, making it easier to isolate changes, track progress, and collaborate on pattern development.

How do I debug pattern context issues during development?

Use `<ct-cell-context>` as a targeted debugging aid to annotate values in context during pattern development. This helps isolate context-related problems without disrupting the broader development workflow or requiring full deployment cycles.

What should I do when updating labs framework dependencies?

Restart dev servers when updating labs to ensure changes take effect. The pattern development workflow includes guidelines for managing dev server lifecycle, preventing stale contexts and ensuring your local environment reflects the latest framework state.

Can I use pattern development best practices across multiple team members?

Yes. Pattern development workflow applies to teams actively developing patterns in labs. It covers communication guidelines, naming conventions, commit discipline, and deployment workflows—designed to scale across collaborative pattern development efforts.