@ngxtm/devkit 3.7.0 → 3.9.0

package/merged-commands/conductor-status.md

@@ -0,0 +1,338 @@
+---
+name: conductor-status
+description: Display project status, active tracks, and next actions
+metadata:
+  argument-hint: "[track-id] [--detailed]"
+---
+
+# Conductor Status
+
+Display the current status of the Conductor project, including overall progress, active tracks, and next actions.
+
+## Use this skill when
+
+- Working on conductor status tasks or workflows
+- Needing guidance, best practices, or checklists for conductor status
+
+## Do not use this skill when
+
+- The task is unrelated to conductor status
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Pre-flight Checks
+
+1. Verify Conductor is initialized:
+   - Check `conductor/product.md` exists
+   - Check `conductor/tracks.md` exists
+   - If missing: Display error and suggest running `/conductor:setup` first
+
+2. Check for any tracks:
+   - Read `conductor/tracks.md`
+   - If no tracks registered: Display setup complete message with suggestion to create first track
+
+## Data Collection
+
+### 1. Project Information
+
+Read `conductor/product.md` and extract:
+
+- Project name
+- Project description
+
+### 2. Tracks Overview
+
+Read `conductor/tracks.md` and parse:
+
+- Total tracks count
+- Completed tracks (marked `[x]`)
+- In-progress tracks (marked `[~]`)
+- Pending tracks (marked `[ ]`)
+
+### 3. Detailed Track Analysis
+
+For each track in `conductor/tracks/`:
+
+Read `conductor/tracks/{trackId}/plan.md`:
+
+- Count total tasks (lines matching `- [x]`, `- [~]`, `- [ ]` with Task prefix)
+- Count completed tasks (`[x]`)
+- Count in-progress tasks (`[~]`)
+- Count pending tasks (`[ ]`)
+- Identify current phase (first phase with incomplete tasks)
+- Identify next pending task
+
+Read `conductor/tracks/{trackId}/metadata.json`:
+
+- Track type (feature, bug, chore, refactor)
+- Created date
+- Last updated date
+- Status
+
+Read `conductor/tracks/{trackId}/spec.md`:
+
+- Check for any noted blockers or dependencies
+
+### 4. Blocker Detection
+
+Scan for potential blockers:
+
+- Tasks marked with `BLOCKED:` prefix
+- Dependencies on incomplete tracks
+- Failed verification tasks
+
+## Output Format
+
+### Full Project Status (no argument)
+
+```
+================================================================================
+                        PROJECT STATUS: {Project Name}
+================================================================================
+Last Updated: {current timestamp}
+
+--------------------------------------------------------------------------------
+                              OVERALL PROGRESS
+--------------------------------------------------------------------------------
+
+Tracks:     {completed}/{total} completed ({percentage}%)
+Tasks:      {completed}/{total} completed ({percentage}%)
+
+Progress:   [##########..........] {percentage}%
+
+--------------------------------------------------------------------------------
+                              TRACK SUMMARY
+--------------------------------------------------------------------------------
+
+| Status | Track ID          | Type    | Tasks      | Last Updated |
+|--------|-------------------|---------|------------|--------------|
+| [x]    | auth_20250110     | feature | 12/12 (100%)| 2025-01-12  |
+| [~]    | dashboard_20250112| feature | 7/15 (47%) | 2025-01-15  |
+| [ ]    | nav-fix_20250114  | bug     | 0/4 (0%)   | 2025-01-14  |
+
+--------------------------------------------------------------------------------
+                              CURRENT FOCUS
+--------------------------------------------------------------------------------
+
+Active Track:  dashboard_20250112 - Dashboard Feature
+Current Phase: Phase 2: Core Components
+Current Task:  [~] Task 2.3: Implement chart rendering
+
+Progress in Phase:
+  - [x] Task 2.1: Create dashboard layout
+  - [x] Task 2.2: Add data fetching hooks
+  - [~] Task 2.3: Implement chart rendering
+  - [ ] Task 2.4: Add filter controls
+
+--------------------------------------------------------------------------------
+                              NEXT ACTIONS
+--------------------------------------------------------------------------------
+
+1. Complete: Task 2.3 - Implement chart rendering (dashboard_20250112)
+2. Then: Task 2.4 - Add filter controls (dashboard_20250112)
+3. After Phase 2: Phase verification checkpoint
+
+--------------------------------------------------------------------------------
+                               BLOCKERS
+--------------------------------------------------------------------------------
+
+{If blockers found:}
+! BLOCKED: Task 3.1 in dashboard_20250112 depends on api_20250111 (incomplete)
+
+{If no blockers:}
+No blockers identified.
+
+================================================================================
+Commands: /conductor:implement {trackId} | /conductor:new-track | /conductor:revert
+================================================================================
+```
+
+### Single Track Status (with track-id argument)
+
+```
+================================================================================
+                    TRACK STATUS: {Track Title}
+================================================================================
+Track ID:    {trackId}
+Type:        {feature|bug|chore|refactor}
+Status:      {Pending|In Progress|Complete}
+Created:     {date}
+Updated:     {date}
+
+--------------------------------------------------------------------------------
+                              SPECIFICATION
+--------------------------------------------------------------------------------
+
+Summary: {brief summary from spec.md}
+
+Acceptance Criteria:
+  - [x] {Criterion 1}
+  - [ ] {Criterion 2}
+  - [ ] {Criterion 3}
+
+--------------------------------------------------------------------------------
+                              IMPLEMENTATION
+--------------------------------------------------------------------------------
+
+Overall:    {completed}/{total} tasks ({percentage}%)
+Progress:   [##########..........] {percentage}%
+
+## Phase 1: {Phase Name} [COMPLETE]
+  - [x] Task 1.1: {description}
+  - [x] Task 1.2: {description}
+  - [x] Verification: {description}
+
+## Phase 2: {Phase Name} [IN PROGRESS]
+  - [x] Task 2.1: {description}
+  - [~] Task 2.2: {description}  <-- CURRENT
+  - [ ] Task 2.3: {description}
+  - [ ] Verification: {description}
+
+## Phase 3: {Phase Name} [PENDING]
+  - [ ] Task 3.1: {description}
+  - [ ] Task 3.2: {description}
+  - [ ] Verification: {description}
+
+--------------------------------------------------------------------------------
+                              GIT HISTORY
+--------------------------------------------------------------------------------
+
+Related Commits:
+  abc1234 - feat: add login form ({trackId})
+  def5678 - feat: add password validation ({trackId})
+  ghi9012 - chore: mark task 1.2 complete ({trackId})
+
+--------------------------------------------------------------------------------
+                              NEXT STEPS
+--------------------------------------------------------------------------------
+
+1. Current: Task 2.2 - {description}
+2. Next: Task 2.3 - {description}
+3. Phase 2 verification pending
+
+================================================================================
+Commands: /conductor:implement {trackId} | /conductor:revert {trackId}
+================================================================================
+```
+
+## Status Markers Legend
+
+Display at bottom if helpful:
+
+```
+Legend:
+  [x] = Complete
+  [~] = In Progress
+  [ ] = Pending
+  [!] = Blocked
+```
+
+## Error States
+
+### No Tracks Found
+
+```
+================================================================================
+                        PROJECT STATUS: {Project Name}
+================================================================================
+
+Conductor is set up but no tracks have been created yet.
+
+To get started:
+  /conductor:new-track "your feature description"
+
+================================================================================
+```
+
+### Conductor Not Initialized
+
+```
+ERROR: Conductor not initialized
+
+Could not find conductor/product.md
+
+Run /conductor:setup to initialize Conductor for this project.
+```
+
+### Track Not Found (with argument)
+
+```
+ERROR: Track not found: {argument}
+
+Available tracks:
+  - auth_20250115
+  - dashboard_20250112
+  - nav-fix_20250114
+
+Usage: /conductor:status [track-id]
+```
+
+## Calculation Logic
+
+### Task Counting
+
+```
+For each plan.md:
+  - Complete: count lines matching /^- \[x\] Task/
+  - In Progress: count lines matching /^- \[~\] Task/
+  - Pending: count lines matching /^- \[ \] Task/
+  - Total: Complete + In Progress + Pending
+```
+
+### Phase Detection
+
+```
+Current phase = first phase header followed by any incomplete task ([ ] or [~])
+```
+
+### Progress Bar
+
+```
+filled = floor((completed / total) * 20)
+empty = 20 - filled
+bar = "[" + "#".repeat(filled) + ".".repeat(empty) + "]"
+```
+
+## Quick Mode
+
+If invoked with `--quick` or `-q`:
+
+```
+{Project Name}: {completed}/{total} tasks ({percentage}%)
+Active: {trackId} - Task {X.Y}
+```
+
+## JSON Output
+
+If invoked with `--json`:
+
+```json
+{
+  "project": "{name}",
+  "timestamp": "ISO_TIMESTAMP",
+  "tracks": {
+    "total": N,
+    "completed": X,
+    "in_progress": Y,
+    "pending": Z
+  },
+  "tasks": {
+    "total": M,
+    "completed": A,
+    "in_progress": B,
+    "pending": C
+  },
+  "current": {
+    "track": "{trackId}",
+    "phase": N,
+    "task": "{X.Y}"
+  },
+  "blockers": []
+}
+```

package/merged-commands/conductor-validator.md

@@ -0,0 +1,62 @@
+---
+name: conductor-validator
+description: Validates Conductor project artifacts for completeness,
+  consistency, and correctness. Use after setup, when diagnosing issues, or
+  before implementation to verify project context.
+allowed-tools: Read Glob Grep Bash
+metadata:
+  model: opus
+  color: cyan
+---
+
+# Check if conductor directory exists
+ls -la conductor/
+
+# Find all track directories
+ls -la conductor/tracks/
+
+# Check for required files
+ls conductor/index.md conductor/product.md conductor/tech-stack.md conductor/workflow.md conductor/tracks.md
+```
+
+## Use this skill when
+
+- Working on check if conductor directory exists tasks or workflows
+- Needing guidance, best practices, or checklists for check if conductor directory exists
+
+## Do not use this skill when
+
+- The task is unrelated to check if conductor directory exists
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Pattern Matching
+
+**Status markers in tracks.md:**
+
+```
+- [ ] Track Name  # Not started
+- [~] Track Name  # In progress
+- [x] Track Name  # Complete
+```
+
+**Task markers in plan.md:**
+
+```
+- [ ] Task description  # Pending
+- [~] Task description  # In progress
+- [x] Task description  # Complete
+```
+
+**Track ID pattern:**
+
+```
+<type>_<name>_<YYYYMMDD>
+Example: feature_user_auth_20250115
+```

package/merged-commands/content-creator.md

@@ -0,0 +1,248 @@
+---
+name: content-creator
+description: Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or when user mentions content creation, brand voice, SEO optimization, social media marketing, or content strategy.
+license: MIT
+metadata:
+  version: 1.0.0
+  author: Alireza Rezvani
+  category: marketing
+  domain: content-marketing
+  updated: 2025-10-20
+  python-tools: brand_voice_analyzer.py, seo_optimizer.py
+  tech-stack: SEO, social-media-platforms
+---
+
+# Content Creator
+
+Professional-grade brand voice analysis, SEO optimization, and platform-specific content frameworks.
+
+## Keywords
+content creation, blog posts, SEO, brand voice, social media, content calendar, marketing content, content strategy, content marketing, brand consistency, content optimization, social media marketing, content planning, blog writing, content frameworks, brand guidelines, social media strategy
+
+## Quick Start
+
+### For Brand Voice Development
+1. Run `scripts/brand_voice_analyzer.py` on existing content to establish baseline
+2. Review `references/brand_guidelines.md` to select voice attributes
+3. Apply chosen voice consistently across all content
+
+### For Blog Content Creation
+1. Choose template from `references/content_frameworks.md`
+2. Research keywords for topic
+3. Write content following template structure
+4. Run `scripts/seo_optimizer.py [file] [primary-keyword]` to optimize
+5. Apply recommendations before publishing
+
+### For Social Media Content
+1. Review platform best practices in `references/social_media_optimization.md`
+2. Use appropriate template from `references/content_frameworks.md`
+3. Optimize based on platform-specific guidelines
+4. Schedule using `assets/content_calendar_template.md`
+
+## Core Workflows
+
+### Establishing Brand Voice (First Time Setup)
+
+When creating content for a new brand or client:
+
+1. **Analyze Existing Content** (if available)
+   ```bash
+   python scripts/brand_voice_analyzer.py existing_content.txt
+   ```
+   
+2. **Define Voice Attributes**
+   - Review brand personality archetypes in `references/brand_guidelines.md`
+   - Select primary and secondary archetypes
+   - Choose 3-5 tone attributes
+   - Document in brand guidelines
+
+3. **Create Voice Sample**
+   - Write 3 sample pieces in chosen voice
+   - Test consistency using analyzer
+   - Refine based on results
+
+### Creating SEO-Optimized Blog Posts
+
+1. **Keyword Research**
+   - Identify primary keyword (search volume 500-5000/month)
+   - Find 3-5 secondary keywords
+   - List 10-15 LSI keywords
+
+2. **Content Structure**
+   - Use blog template from `references/content_frameworks.md`
+   - Include keyword in title, first paragraph, and 2-3 H2s
+   - Aim for 1,500-2,500 words for comprehensive coverage
+
+3. **Optimization Check**
+   ```bash
+   python scripts/seo_optimizer.py blog_post.md "primary keyword" "secondary,keywords,list"
+   ```
+
+4. **Apply SEO Recommendations**
+   - Adjust keyword density to 1-3%
+   - Ensure proper heading structure
+   - Add internal and external links
+   - Optimize meta description
+
+### Social Media Content Creation
+
+1. **Platform Selection**
+   - Identify primary platforms based on audience
+   - Review platform-specific guidelines in `references/social_media_optimization.md`
+
+2. **Content Adaptation**
+   - Start with blog post or core message
+   - Use repurposing matrix from `references/content_frameworks.md`
+   - Adapt for each platform following templates
+
+3. **Optimization Checklist**
+   - Platform-appropriate length
+   - Optimal posting time
+   - Correct image dimensions
+   - Platform-specific hashtags
+   - Engagement elements (polls, questions)
+
+### Content Calendar Planning
+
+1. **Monthly Planning**
+   - Copy `assets/content_calendar_template.md`
+   - Set monthly goals and KPIs
+   - Identify key campaigns/themes
+
+2. **Weekly Distribution**
+   - Follow 40/25/25/10 content pillar ratio
+   - Balance platforms throughout week
+   - Align with optimal posting times
+
+3. **Batch Creation**
+   - Create all weekly content in one session
+   - Maintain consistent voice across pieces
+   - Prepare all visual assets together
+
+## Key Scripts
+
+### brand_voice_analyzer.py
+Analyzes text content for voice characteristics, readability, and consistency.
+
+**Usage**: `python scripts/brand_voice_analyzer.py <file> [json|text]`
+
+**Returns**:
+- Voice profile (formality, tone, perspective)
+- Readability score
+- Sentence structure analysis
+- Improvement recommendations
+
+### seo_optimizer.py
+Analyzes content for SEO optimization and provides actionable recommendations.
+
+**Usage**: `python scripts/seo_optimizer.py <file> [primary_keyword] [secondary_keywords]`
+
+**Returns**:
+- SEO score (0-100)
+- Keyword density analysis
+- Structure assessment
+- Meta tag suggestions
+- Specific optimization recommendations
+
+## Reference Guides
+
+### When to Use Each Reference
+
+**references/brand_guidelines.md**
+- Setting up new brand voice
+- Ensuring consistency across content
+- Training new team members
+- Resolving voice/tone questions
+
+**references/content_frameworks.md**
+- Starting any new content piece
+- Structuring different content types
+- Creating content templates
+- Planning content repurposing
+
+**references/social_media_optimization.md**
+- Platform-specific optimization
+- Hashtag strategy development
+- Understanding algorithm factors
+- Setting up analytics tracking
+
+## Best Practices
+
+### Content Creation Process
+1. Always start with audience need/pain point
+2. Research before writing
+3. Create outline using templates
+4. Write first draft without editing
+5. Optimize for SEO
+6. Edit for brand voice
+7. Proofread and fact-check
+8. Optimize for platform
+9. Schedule strategically
+
+### Quality Indicators
+- SEO score above 75/100
+- Readability appropriate for audience
+- Consistent brand voice throughout
+- Clear value proposition
+- Actionable takeaways
+- Proper visual formatting
+- Platform-optimized
+
+### Common Pitfalls to Avoid
+- Writing before researching keywords
+- Ignoring platform-specific requirements
+- Inconsistent brand voice
+- Over-optimizing for SEO (keyword stuffing)
+- Missing clear CTAs
+- Publishing without proofreading
+- Ignoring analytics feedback
+
+## Performance Metrics
+
+Track these KPIs for content success:
+
+### Content Metrics
+- Organic traffic growth
+- Average time on page
+- Bounce rate
+- Social shares
+- Backlinks earned
+
+### Engagement Metrics
+- Comments and discussions
+- Email click-through rates
+- Social media engagement rate
+- Content downloads
+- Form submissions
+
+### Business Metrics
+- Leads generated
+- Conversion rate
+- Customer acquisition cost
+- Revenue attribution
+- ROI per content piece
+
+## Integration Points
+
+This skill works best with:
+- Analytics platforms (Google Analytics, social media insights)
+- SEO tools (for keyword research)
+- Design tools (for visual content)
+- Scheduling platforms (for content distribution)
+- Email marketing systems (for newsletter content)
+
+## Quick Commands
+
+```bash
+# Analyze brand voice
+python scripts/brand_voice_analyzer.py content.txt
+
+# Optimize for SEO
+python scripts/seo_optimizer.py article.md "main keyword"
+
+# Check content against brand guidelines
+grep -f references/brand_guidelines.md content.txt
+
+# Create monthly calendar
+cp assets/content_calendar_template.md this_month_calendar.md
+```