ccstart 2.0.1 → 2.1.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ccstart",
-  "version": "2.0.1",
+  "version": "2.1.0",
   "description": "Start your Claude Code projects with a well-organized structure including agents, tickets, plans and orchestration workflows",
   "bin": {
     "ccstart": "bin/create-project.js"

package/template/claude/CLAUDE.md

@@ -140,8 +140,21 @@ After adding the agents you want to in `./claude/agents` folder, setup the workf
 ## Custom Commands
 
 Custom slash commands are available in `.claude/commands/`:
+
+**Git Workflow:**
+- **/commit** - Generate and execute git commits following conventional commit format
+- **/create-pr** - Create GitHub pull requests with structured descriptions
+- **/review-pr** - Review pull requests with systematic quality checks
+
+**Project Management:**
+- **/create-ticket** - Create task tickets with proper numbering and update ticket-list.md
+- **/design-feature** - Guide feature development through requirements and design phases
+- **/create-plan** - Create timestamped planning documents
+
+**Utilities:**
 - **/update-claude-md** - Automatically updates this file with project-specific information
-- See `.claude/commands/README.md` for creating your own commands
+
+See `.claude/commands/README.md` for creating your own commands
 
 ## Tickets
 

package/template/claude/agents/backend.md

@@ -1,7 +1,6 @@
 ---
 name: backend
 description: Backend development specialist. Use PROACTIVELY for API design, database architecture, authentication, microservices, and server-side optimization. Invoke when building APIs, services, or backend infrastructure.
-tools: Read, Write, Edit, Grep, Glob, Bash, WebSearch, WebFetch
 ---
 
 You are a senior backend engineer with expertise in server-side technologies and distributed systems. Your role is to design and implement scalable, secure, and performant backend services.

package/template/claude/agents/blockchain.md

@@ -1,7 +1,6 @@
 ---
 name: blockchain
 description: Blockchain and Web3 specialist. Use PROACTIVELY for smart contract development, DeFi protocols, blockchain architecture, security audits, and Web3 integrations. Invoke when working with Ethereum, Solana, or other blockchain platforms.
-tools: Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, Bash
 ---
 
 You are a blockchain and Web3 expert specializing in smart contract development, decentralized applications, and blockchain architecture. Your expertise spans multiple blockchain platforms and the entire Web3 ecosystem.

package/template/claude/agents/checker.md

@@ -1,7 +1,6 @@
 ---
 name: checker
 description: Quality assurance and code review specialist. Use PROACTIVELY for testing, debugging, security analysis, and code quality verification. Invoke after code implementation or when you need thorough quality validation.
-tools: Read, Grep, Glob, Bash, TodoRead
 ---
 
 You are a senior quality assurance engineer and security specialist. Your role is to thoroughly review, test, and validate code and systems to ensure they meet quality, security, and performance standards.

package/template/claude/agents/coder.md

@@ -1,7 +1,6 @@
 ---
 name: coder
 description: Expert software developer and implementation specialist. Use PROACTIVELY for writing, refactoring, and optimizing code. Invoke when you need to implement features, fix bugs, or improve code quality.
-tools: Read, Edit, Write, Grep, Glob, Bash, TodoRead
 ---
 
 You are a senior software engineer with expertise across multiple programming languages and frameworks. Your role is to implement high-quality, maintainable code based on specifications and plans.

package/template/claude/agents/frontend.md

@@ -1,7 +1,6 @@
 ---
 name: frontend
 description: Frontend development specialist. Use PROACTIVELY for UI/UX implementation, responsive design, state management, and frontend performance optimization. Invoke when building user interfaces, SPAs, or frontend features.
-tools: Read, Write, Edit, Grep, Glob, Bash, WebSearch, WebFetch
 ---
 
 You are a senior frontend engineer with expertise in modern web technologies and user interface development. Your role is to create beautiful, performant, and accessible user interfaces.

package/template/claude/agents/planner.md

@@ -1,7 +1,6 @@
 ---
 name: planner
 description: Strategic planning specialist. Use PROACTIVELY for breaking down complex problems, creating implementation roadmaps, and architectural planning. Invoke when you need to plan a feature, design system architecture, or break down large tasks.
-tools: Read, Grep, Glob, TodoWrite
 ---
 
 You are a strategic planning and system architecture expert. Your primary role is to analyze requirements, break down complex problems into manageable tasks, and create clear implementation roadmaps.

package/template/claude/agents/researcher.md

@@ -1,7 +1,6 @@
 ---
 name: researcher
 description: Research and investigation specialist for both online sources and local codebases. Use PROACTIVELY for researching documentation, APIs, best practices online AND deep-diving into local code. Invoke when you need comprehensive information from multiple sources.
-tools: Read, Grep, Glob, LS, WebSearch, WebFetch
 ---
 
 You are a research and investigation specialist with expertise in both online research and local codebase analysis. Your primary role is to gather comprehensive information from all available sources to support informed decision-making.

package/template/claude/agents/shadcn.md

@@ -1,7 +1,6 @@
 ---
 name: shadcn
 description: shadcn/ui component library specialist. Use PROACTIVELY for building beautiful, accessible React interfaces with shadcn/ui, Radix UI, and Tailwind CSS. Invoke when implementing modern UI components with best-in-class accessibility.
-tools: Read, Write, Edit, Grep, Glob, Bash, WebSearch, WebFetch
 ---
 
 You are a shadcn/ui specialist with deep expertise in building modern React interfaces using the shadcn/ui component library, Radix UI primitives, and Tailwind CSS. Your role is to create beautiful, accessible, and customizable user interfaces.

package/template/claude/skills/commit/SKILL.md

@@ -0,0 +1,97 @@
+---
+name: commit
+description: Generate and execute git commits following conventional commit format. Use when the user wants to commit changes, create a commit, or says "/commit". Analyzes staged/unstaged changes and creates properly formatted commit messages with type, optional scope, and descriptive subject.
+---
+
+# Commit Skill
+
+Generate conventional commit messages and execute commits automatically.
+
+## Workflow
+
+1. Run `git status` (never use `-uall` flag) and `git diff` to analyze changes
+2. Run `git log --oneline -5` to see recent commit style
+3. Determine the appropriate commit type and scope from the changes
+4. Stage all relevant changes with `git add`
+5. Create the commit with a properly formatted message
+
+## Commit Format
+
+```
+<type>(<scope>): <subject>
+
+<body>
+
+<footer>
+```
+
+### Types
+
+| Type | Use for |
+|------|---------|
+| `feat` | New feature or functionality |
+| `fix` | Bug fix |
+| `docs` | Documentation only |
+| `style` | Formatting, semicolons, no code change |
+| `refactor` | Code change that neither fixes nor adds |
+| `test` | Adding or modifying tests |
+| `chore` | Maintenance, deps, build process |
+| `perf` | Performance improvements |
+
+### Scope
+
+Optional. Include when it adds clarity about what area is affected:
+- `feat(auth):` - authentication related
+- `fix(api):` - API related
+- `docs:` - scope omitted when obvious
+
+### Subject
+
+- Imperative mood ("add" not "added" or "adds")
+- No period at end
+- Max 50 characters
+- Focus on the "why" not the "what"
+
+### Body (optional)
+
+Add when the subject alone doesn't fully explain the change. Wrap at 72 characters.
+
+### Footer (optional)
+
+- Breaking changes: `BREAKING CHANGE: description`
+- Issue references: `Closes #123`
+
+## Commit Message Construction
+
+Use a HEREDOC for proper formatting:
+
+```bash
+git commit -m "$(cat <<'EOF'
+<type>(<scope>): <subject>
+
+<body if needed>
+EOF
+)"
+```
+
+## Examples
+
+Single file change:
+```
+fix(auth): handle expired tokens gracefully
+```
+
+Multiple related changes:
+```
+feat(api): add email notifications for shipped orders
+
+Send confirmation email when order status changes to shipped.
+Includes tracking number and estimated delivery date.
+```
+
+Breaking change:
+```
+refactor(config)!: migrate to environment-based configuration
+
+BREAKING CHANGE: config.json no longer supported, use .env files
+```

package/template/claude/skills/create-pr/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: create-pr
+description: Create GitHub pull requests with properly structured descriptions. Use when the user explicitly asks to create a PR, open a pull request, or says "/create-pr". Analyzes commits and changes to generate clear PR descriptions with summary, changes list, and UI changes when applicable.
+---
+
+# Create PR Skill
+
+Create GitHub pull requests with structured descriptions.
+
+## Workflow
+
+1. Run `git status` to check for uncommitted changes and remote tracking
+2. Run `git diff <base-branch>...HEAD` to see all changes since branching
+3. Run `git log <base-branch>..HEAD --oneline` to see all commits
+4. Analyze changes to draft PR title and description
+5. Push branch if needed with `git push -u origin <branch>`
+6. Create PR with `gh pr create`
+
+## PR Format
+
+**Title:** Use conventional commit format: `<type>(<scope>): <subject>`
+
+**Body:**
+```markdown
+## Summary
+<What this PR does and why - 1-3 sentences>
+
+## Changes
+- <Specific change 1>
+- <Specific change 2>
+- <Specific change 3>
+
+## UI Changes
+<Text description of visual/layout changes - omit section if no UI changes>
+```
+
+## Creating the PR
+
+Use HEREDOC for proper formatting:
+
+```bash
+gh pr create --title "<type>(<scope>): <subject>" --body "$(cat <<'EOF'
+## Summary
+<description>
+
+## Changes
+- <change 1>
+- <change 2>
+EOF
+)"
+```
+
+## Examples
+
+**Backend PR:**
+```markdown
+## Summary
+Add email notifications when orders are shipped. Customers receive
+an automated email with tracking information when their order status
+changes to "shipped".
+
+## Changes
+- Add `ShippingNotificationService` to handle email dispatch
+- Integrate with SendGrid API for email delivery
+- Add email template for shipping confirmation
+- Update `OrderController` to trigger notification on status change
+```
+
+**PR with UI changes:**
+```markdown
+## Summary
+Add dark mode toggle to application settings.
+
+## Changes
+- Add `ThemeContext` for managing theme state
+- Create `DarkModeToggle` component in settings page
+- Update CSS variables for dark theme colors
+- Persist theme preference to localStorage
+
+## UI Changes
+- New toggle switch in Settings > Appearance section
+- Toggle positioned right-aligned with "Dark Mode" label on left
+- Switch uses primary brand color when enabled
+```

package/template/claude/skills/create-ticket/SKILL.md

@@ -0,0 +1,102 @@
+---
+name: create-ticket
+description: Create task tickets with proper numbering, template structure, and ticket-list.md updates. Use when the user wants to create a ticket, add a task, or says "/create-ticket". Automatically finds the next ticket number, creates the ticket file, and updates the centralized ticket list.
+---
+
+# Create Ticket Skill
+
+Create properly numbered tickets with consistent structure.
+
+## Workflow
+
+1. Scan `claude/tickets/` for existing `TICKET-XXX-*.md` files
+2. Determine next ticket number (highest + 1, or 001 if none)
+3. Create ticket file at `claude/tickets/TICKET-XXX-description.md`
+4. Update `claude/tickets/ticket-list.md` with new entry
+
+## Finding Next Ticket Number
+
+```bash
+ls claude/tickets/TICKET-*.md 2>/dev/null | grep -oE 'TICKET-[0-9]+' | sort -t'-' -k2 -n | tail -1
+```
+
+If no tickets exist, start with `TICKET-001`.
+
+## Ticket Template
+
+```markdown
+# TICKET-XXX: [Title]
+
+## Description
+[Detailed description of the task]
+
+## Acceptance Criteria
+- [ ] Criterion 1
+- [ ] Criterion 2
+- [ ] Criterion 3
+
+## Priority
+High/Medium/Low
+
+## Status
+Todo
+
+## Notes
+[Any additional context or notes]
+```
+
+## Updating ticket-list.md
+
+Add entry to appropriate priority section:
+
+```markdown
+### High Priority
+- 🔴 [TICKET-XXX](./TICKET-XXX-description.md) - Title here
+```
+
+**Status emojis:**
+| Status | Emoji |
+|--------|-------|
+| Todo | 🔴 |
+| In Progress | 🟡 |
+| Done | 🟢 |
+| Blocked | 🔵 |
+| Cancelled | ⚫ |
+
+## File Naming
+
+Convert title to kebab-case for filename:
+- "User Authentication" → `TICKET-001-user-authentication.md`
+- "Fix API Bug" → `TICKET-002-fix-api-bug.md`
+
+## Example
+
+User: "Create a ticket for adding user authentication"
+
+Creates `claude/tickets/TICKET-001-user-authentication.md`:
+```markdown
+# TICKET-001: User Authentication
+
+## Description
+Implement user authentication system for the application.
+
+## Acceptance Criteria
+- [ ] Users can register with email/password
+- [ ] Users can log in and receive session token
+- [ ] Protected routes require authentication
+
+## Priority
+High
+
+## Status
+Todo
+
+## Notes
+Consider using JWT for session management.
+```
+
+Updates `claude/tickets/ticket-list.md`:
+```markdown
+### High Priority
+- 🔴 [TICKET-001](./TICKET-001-user-authentication.md) - User Authentication
+```

package/template/claude/skills/design-feature/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: design-feature
+description: Guide feature development through contract establishment and UI design phases. Use when discussing, designing, or planning a new feature that is not yet implemented. Ensures requirements are clarified, acceptance criteria defined, and UI layouts drafted before any code is written.
+---
+
+# Design Feature Skill
+
+Guide new feature development through structured planning phases before implementation.
+
+## Workflow
+
+### Phase 1: Contract Establishment
+
+Before any design or code, establish the feature contract:
+
+1. **Clarify requirements** - Ask questions to fully understand the feature
+2. **Define scope** - What is and isn't included
+3. **Set acceptance criteria** - Specific, testable conditions for completion
+4. **Identify constraints** - Technical limitations, dependencies, edge cases
+
+Output a contract summary:
+
+```markdown
+## Feature Contract: [Feature Name]
+
+### Scope
+- [What's included]
+- [What's excluded]
+
+### Acceptance Criteria
+- [ ] Criterion 1
+- [ ] Criterion 2
+- [ ] Criterion 3
+
+### Constraints
+- [Technical constraints]
+- [Dependencies]
+```
+
+### Phase 2: UI Design
+
+After contract agreement, draft the UI layout in `claude/docs/UI_LAYOUT.md`.
+
+Include:
+
+1. **Desktop layout** - Full-width design
+2. **Mobile layout** - Responsive/stacked design
+3. **Component hierarchy** - Parent-child relationships
+4. **Interactions** - User actions and responses
+5. **Required assets** - Icons, images, fonts
+
+UI Layout template:
+
+```markdown
+# [Feature Name] - UI Layout
+
+## Desktop Layout
+
+```
+┌─────────────────────────────────────┐
+│  Header                             │
+├─────────────────────────────────────┤
+│  Component A    │  Component B      │
+│                 │                   │
+├─────────────────────────────────────┤
+│  Footer                             │
+└─────────────────────────────────────┘
+```
+
+## Mobile Layout
+
+```
+┌─────────────┐
+│  Header     │
+├─────────────┤
+│ Component A │
+├─────────────┤
+│ Component B │
+├─────────────┤
+│  Footer     │
+└─────────────┘
+```
+
+## Component Hierarchy
+
+- ParentComponent
+  - ChildComponent1
+  - ChildComponent2
+    - GrandchildComponent
+
+## Interactions
+
+| Action | Response |
+|--------|----------|
+| Click X | Shows Y |
+| Hover Z | Highlights |
+
+## Required Assets
+
+- [ ] Icon: description
+- [ ] Image: description
+```
+
+## Process Flow
+
+1. User describes feature idea
+2. Ask clarifying questions (no assumptions)
+3. Draft and agree on contract
+4. Draft UI layout in `claude/docs/UI_LAYOUT.md`
+5. Review UI together, adjust as needed
+6. Only after agreement, proceed to implementation