@nextsparkjs/core 0.1.0-beta.13 → 0.1.0-beta.130

package/dist/presets/ai-workflow/claude/commands/doc:feature.md

@@ -1,427 +0,0 @@
----
-description: Generate comprehensive documentation for a completed feature using session workflow
----
-
-# Document Feature - Generate Documentation
-
-You are generating documentation for a completed and approved feature.
-
-**Session Path or Feature Name:**
-{{{ input }}}
-
----
-
-## Your Mission
-
-Generate comprehensive documentation for a completed feature:
-
-1. **Validate completion** (QA passed, code reviewed)
-2. **Read session files** to understand the feature
-3. **Validate against code** (not just plan)
-4. **Determine documentation tier** (core, theme, plugin)
-5. **Create/update documentation** in appropriate location
-
----
-
-## Prerequisites
-
-**CRITICAL**: Only use this command for features that have:
-- ✅ Passed QA testing (qa-automation marked as ✅ Completado)
-- ✅ Passed code review (code-reviewer marked as ✅ Completado)
-- ✅ Been approved by stakeholders
-
-**DO NOT use for:**
-- Features still in development
-- Features that haven't been tested
-- Features with failing tests
-
----
-
-## Documentation Protocol
-
-### Step 1: Locate Session
-
-```typescript
-const input = '{{{ input }}}'
-
-// Determine session path
-let sessionPath
-if (input.includes('.claude/sessions/')) {
-  sessionPath = input
-} else {
-  // Search for session by name
-  const sessions = await Glob('.claude/sessions/*/')
-  sessionPath = sessions.find(s => s.includes(input))
-}
-
-if (!sessionPath) {
-  throw new Error(`Session not found: ${input}`)
-}
-```
-
-### Step 2: Validate Completion
-
-```typescript
-// Read context.md to check completion status
-await Read(`${sessionPath}/context.md`)
-
-// Verify QA completed
-const qaComplete = context.includes('qa-automation') &&
-                   (context.includes('✅ Completado') || context.includes('✅ Tests Passed'))
-
-// Verify Code Review completed
-const crComplete = context.includes('code-reviewer') &&
-                   (context.includes('✅ Completado') || context.includes('⚠️ Aprobado'))
-
-if (!qaComplete || !crComplete) {
-  console.log(`
-⚠️ Advertencia: Feature no completamente aprobado
-
-Estado actual:
-- QA Testing: ${qaComplete ? '✅' : '⚠️ Pendiente'}
-- Code Review: ${crComplete ? '✅' : '⚠️ Pendiente'}
-
-¿Continuar de todas formas? (Solo recomendado si ambos están ✅)
-`)
-}
-```
-
-### Step 3: Read Session Files
-
-```typescript
-// Read all session documentation
-const requirements = await Read(`${sessionPath}/requirements.md`)
-const clickupTask = await Read(`${sessionPath}/clickup_task.md`)
-const plan = await Read(`${sessionPath}/plan.md`)
-const progress = await Read(`${sessionPath}/progress.md`)
-const tests = await Read(`${sessionPath}/tests.md`)
-
-// Extract key information
-const featureName = extractFeatureName(requirements)
-const acceptanceCriteria = extractACs(clickupTask)
-const technicalPlan = extractPlan(plan)
-const implementedFiles = extractFilesFromProgress(progress)
-const testResults = extractTestResults(tests)
-```
-
-### Step 4: Validate Against Code
-
-```typescript
-// CRITICAL: Session files may differ from actual implementation
-
-for (const file of implementedFiles) {
-  const actualCode = await Read(file)
-
-  // Verify:
-  // - File exists
-  // - Functions/components match description
-  // - API endpoints work as documented
-  // - Props/parameters are accurate
-}
-
-// Extract real implementation details
-const apiEndpoints = await Glob('app/api/v1/**/*.ts')
-const components = await Glob('app/components/**/*.tsx')
-```
-
-### Step 5: Determine Documentation Tier
-
-```typescript
-// Based on where code was implemented
-function determineTier(files) {
-  const tiers = {
-    core: files.some(f => f.startsWith('core/')),
-    theme: files.some(f => f.includes('contents/themes/')),
-    plugin: files.some(f => f.includes('contents/plugins/'))
-  }
-
-  // A feature can require documentation in multiple tiers
-  return Object.entries(tiers)
-    .filter(([_, included]) => included)
-    .map(([tier]) => tier)
-}
-
-// Documentation locations
-const docLocations = {
-  core: 'core/docs/',
-  theme: (theme) => `contents/themes/${theme}/docs/`,
-  plugin: (plugin) => `contents/plugins/${plugin}/docs/`
-}
-```
-
-### Step 6: Launch Documentation Writer
-
-```typescript
-await launchAgent('documentation-writer', {
-  task: `Generate documentation for: ${featureName}`,
-  requirements: [
-    'Read session files for context (READ-ONLY)',
-    'Validate against actual implementation code',
-    'Create documentation in appropriate tier(s)',
-    'Follow documentation system structure',
-    'Include working code examples from real implementation',
-    'Add API reference with actual endpoints',
-    'Include troubleshooting from QA feedback',
-    'Do NOT modify session files'
-  ],
-  sessionPath: sessionPath,
-  tiers: determineTier(implementedFiles)
-})
-```
-
----
-
-## Documentation Structure
-
-### Core Documentation
-
-**Location:** `core/docs/{section-number}-{topic}/`
-
-```markdown
----
-title: Feature Name
-description: Brief description of the feature
----
-
-## Overview
-
-What this feature does and why it exists.
-
-## Prerequisites
-
-- Required dependencies
-- Environment setup
-
-## Installation
-
-Step-by-step installation if needed.
-
-## Usage
-
-### Basic Usage
-
-\`\`\`typescript
-// Real code example from implementation
-\`\`\`
-
-### Advanced Usage
-
-\`\`\`typescript
-// More complex example
-\`\`\`
-
-## API Reference
-
-### Endpoints
-
-| Method | Endpoint | Description |
-|--------|----------|-------------|
-| GET | /api/v1/resource | List all |
-| POST | /api/v1/resource | Create new |
-
-### Request/Response
-
-\`\`\`typescript
-// Request
-{
-  "name": "string",
-  "description": "string"
-}
-
-// Response
-{
-  "data": { ... },
-  "success": true
-}
-\`\`\`
-
-## Components
-
-### ComponentName
-
-\`\`\`typescript
-interface Props {
-  prop1: string
-  prop2?: number
-}
-\`\`\`
-
-**Usage:**
-\`\`\`tsx
-<ComponentName prop1="value" />
-\`\`\`
-
-## Configuration
-
-Available configuration options.
-
-## Database Schema
-
-If database changes were made.
-
-## Internationalization
-
-Translation keys used.
-
-## Testing
-
-How to test this feature.
-
-## Troubleshooting
-
-Common issues and solutions (from QA feedback).
-
-## Related
-
-Links to related documentation.
-```
-
----
-
-## Output Format
-
-```markdown
-## Documentation Generated
-
-**Feature:** ${featureName}
-**Session:** \`${sessionPath}\`
-
-### Documentation Created
-
-📚 **Core Documentation:**
-- Location: \`${coreDocPath}\`
-- Sections: Overview, API Reference, Components
-
-🎨 **Theme Documentation:**
-- Location: \`${themeDocPath}\`
-- Sections: UI Components, Styling
-
-🧩 **Plugin Documentation:**
-- Location: \`${pluginDocPath}\`
-- Sections: Installation, Configuration
-
-### Validation
-
-- ✅ Code verified vs session plan
-- ✅ Examples extracted from real implementation
-- ✅ API Reference validated against endpoints
-- ✅ Test results incorporated
-
-### Files Created
-
-${createdFiles.map(f => `- \`${f}\``).join('\n')}
-
-### Next Steps
-
-1. Review generated documentation
-2. Rebuild docs registry: \`pnpm docs:build\`
-3. Preview at /docs
-4. Collect user feedback for improvements
-```
-
----
-
-## Documentation Tiers Reference
-
-### Core Docs Sections
-
-```
-01 - fundamentals
-02 - getting-started
-03 - registry-system
-04 - api
-05 - authentication
-06 - themes
-07 - plugins
-08 - frontend
-09 - backend
-10 - i18n
-11 - testing
-12 - performance
-13 - deployment
-```
-
-### Theme Docs Sections
-
-```
-01 - overview
-02 - components
-03 - features
-04 - customization
-05 - examples
-```
-
-### Plugin Docs Sections
-
-```
-01 - overview
-02 - installation
-03 - configuration
-04 - api
-05 - examples
-```
-
----
-
-## Best Practices
-
-### DO:
-- Validate code matches session description
-- Extract real examples from implementation
-- Include troubleshooting from QA
-- Cross-reference related docs
-- Use clear, concise language
-
-### DON'T:
-- Copy session files as documentation
-- Include implementation details users don't need
-- Skip code validation
-- Document features that aren't complete
-- Modify session files
-
----
-
-## Error Handling
-
-### Session Not Found
-
-```
-❌ Error: Session not found for '${featureName}'
-
-The folder .claude/sessions/${featureName}/ does not exist.
-
-Solutions:
-1. Verify the feature name (use kebab-case)
-2. List available sessions: ls .claude/sessions/
-3. Run /task:plan to create a new session
-```
-
-### Feature Not Complete
-
-```
-⚠️ Warning: Feature '${featureName}' not fully completed
-
-Current status:
-- QA Testing: ${qaStatus}
-- Code Review: ${crStatus}
-
-Recommendation: Wait for QA and Code Review to complete before documenting.
-
-Continue anyway? (y/n)
-```
-
-### Code Mismatch
-
-```
-⚠️ Warning: Implementation differs from session plan
-
-Discrepancies found:
-- ${discrepancy1}
-- ${discrepancy2}
-
-Documentation will reflect ACTUAL implementation, not plan.
-```
-
----
-
-**Now generate documentation for the feature/session described above.**

package/dist/presets/ai-workflow/claude/commands/doc:read.md

@@ -1,278 +0,0 @@
----
-description: "Gain context by reading documentation before working on a task"
----
-
-# Documentation Context Reader
-
-You are preparing to work on a task by reading the project documentation systematically.
-
-**Topic/Area to Learn:**
-{{{ input }}}
-
----
-
-## Your Mission
-
-Gain comprehensive context about this project before working on any task. This is a **READ-ONLY** operation - you will read documentation, compare with code, and report your understanding.
-
----
-
-## Step 1: Understand Project Context
-
-**CRITICAL:** This is a **CORE BOILERPLATE** used to develop multiple projects.
-
-Key concepts:
-- The `core/` directory contains shared, reusable code that should NEVER be modified for specific projects
-- All project-specific development happens in **THEMES** located at `contents/themes/{theme-name}/`
-- Plugins extend functionality and live in `contents/plugins/`
-
-### Determine Active Theme
-
-```bash
-# Read from .env file
-grep NEXT_PUBLIC_ACTIVE_THEME .env
-```
-
-The active theme determines:
-- Which configuration files are loaded
-- Which entities are available
-- Which UI components and styles are used
-- Which tests are executed
-
-**IMPORTANT:** Always work within the active theme's scope UNLESS the user explicitly specifies a different theme.
-
----
-
-## Step 2: Read Fundamentals (MANDATORY)
-
-**ALWAYS read these files first**, in order:
-
-```
-core/docs/01-fundamentals/
-├── 01-project-overview.md      # Technology stack, core systems
-├── 02-core-lib-organization.md # Directory structure, registries
-├── 03-directory-structure.md   # Root level organization
-├── 04-architecture-patterns.md # Registry pattern, build-time generation
-├── 05-typescript-standards.md  # TypeScript conventions
-└── 06-development-workflow.md  # Claude workflow, agents, commands
-```
-
-Read these files to understand:
-- Technology stack (Next.js 15, React 19, TypeScript, PostgreSQL, Better Auth)
-- 8 core systems (Entity, API, Auth, Registry, Theme, Plugin, Billing, Page Builder)
-- Registry-based loading pattern (zero runtime I/O, 17,255x performance improvement)
-- Directory structure (core vs contents separation)
-- Development workflow with 24 specialized agents
-
----
-
-## Step 3: Read Topic-Specific Documentation
-
-Based on the user's request `{{{ input }}}`, identify and read relevant documentation sections:
-
-### Documentation Directory Map
-
-| Keywords in Request | Documentation to Read |
-|---------------------|----------------------|
-| auth, login, session, password, oauth, permissions, roles | `core/docs/06-authentication/`, `core/docs/14-permissions/` |
-| api, endpoint, route, handler, REST | `core/docs/05-api/` |
-| entity, entities, crud, model, schema | `core/docs/04-entities/`, `core/docs/03-registry-system/` |
-| theme, theming, config, styling | `core/docs/07-theme-system/` |
-| plugin, extension, addon | `core/docs/08-plugin-system/` |
-| test, testing, cypress, jest, e2e, unit | `core/docs/12-testing/` |
-| frontend, ui, component, react, hook | `core/docs/09-frontend/` |
-| database, migration, sql, postgres | `core/docs/10-backend/` |
-| team, teams, multi-tenant, member | `core/docs/10-teams/` |
-| i18n, translation, locale, language | `core/docs/11-internationalization/` |
-| performance, optimization, speed | `core/docs/13-performance/` |
-| deploy, deployment, production, vercel | `core/docs/14-deployment/` |
-| billing, stripe, subscription, payment | `core/docs/19-billing/` |
-| block, blocks, page-builder, builder | `core/docs/18-page-builder/` |
-| workflow, claude, agent, command | `core/docs/16-claude-workflow/` |
-| registry, registries, auto-generated | `core/docs/03-registry-system/` |
-| (general or no specific topic) | `core/docs/01-fundamentals/`, `core/docs/02-getting-started/` |
-
-### Reading Protocol
-
-1. **Identify** the relevant documentation directories based on keywords
-2. **List** all files in those directories
-3. **Read** files in numerical order (01-, 02-, 03-, etc.)
-4. **Note** any cross-references to other documentation sections
-5. **Follow** cross-references if they're relevant to the task
-
----
-
-## Step 4: Compare Documentation vs Code
-
-After reading documentation, **verify accuracy** by reading actual code:
-
-### Verification Checklist
-
-For each documented feature/pattern:
-
-1. **Locate the code** mentioned in the documentation
-   ```
-   Example: If docs mention "PermissionService.canDoAction()"
-   → Read: core/lib/services/permission.service.ts
-   ```
-
-2. **Compare** documented behavior with actual implementation:
-   - Are function signatures accurate?
-   - Are configuration options up to date?
-   - Are file paths correct?
-   - Are examples still valid?
-
-3. **Check** for recent changes:
-   - Look at file modification dates
-   - Check if documented features still exist
-   - Verify imports and exports match documentation
-
-### Key Code Locations to Verify
-
-| Documentation Topic | Code to Verify |
-|--------------------|----------------|
-| Authentication | `core/lib/auth/`, `app/lib/auth.ts` |
-| Permissions | `core/lib/services/permission.service.ts`, `core/lib/registries/permissions-registry.ts` |
-| Entities | `core/lib/entities/`, `contents/themes/{theme}/entities/` |
-| API Routes | `app/api/`, `core/lib/api/` |
-| Configuration | `core/lib/config/`, `contents/themes/{theme}/config/` |
-| Services | `core/lib/services/` |
-| Registries | `core/lib/registries/` (auto-generated) |
-| Components | `core/components/`, `contents/themes/{theme}/components/` |
-
----
-
-## Step 5: Report Status
-
-After completing the reading and verification, report ONE of these statuses:
-
-### Status A: Coherent (Ready to Work)
-
-If documentation matches code and you understand the topic:
-
-```
-## Context Acquired
-
-I have read and understood the documentation for **{topic}**.
-
-**Documentation Read:**
-- core/docs/01-fundamentals/ (6 files)
-- core/docs/{relevant-section}/ (X files)
-
-**Code Verified:**
-- {list of verified code files}
-
-**Active Theme:** {theme-name}
-
-**Summary:**
-{2-3 sentence summary of key concepts learned}
-
-I have the context needed to work on this task.
-```
-
----
-
-### Status B: Ambiguities Found
-
-If there are subtle differences or unclear areas:
-
-```
-## Context Acquired with Notes
-
-I have read the documentation for **{topic}** but found some ambiguities.
-
-**Documentation Read:**
-- {list of files}
-
-**Ambiguities/Questions:**
-1. {Description of ambiguity} - Found in {file}, line ~{N}
-2. {Another ambiguity}
-
-**Impact:**
-{How this might affect the task}
-
-**Recommendation:**
-Please clarify these points before I proceed, or I can proceed with {assumption}.
-```
-
----
-
-### Status C: Documentation Errors Found
-
-If documentation is incorrect or significantly outdated:
-
-```
-## Documentation Issues Detected
-
-While reading documentation for **{topic}**, I found errors that should be corrected.
-
-**Issues Found:**
-
-### Issue 1: {Title}
-- **Location:** `{file-path}`, line ~{N}
-- **Documentation says:** {what docs say}
-- **Code actually does:** {what code does}
-- **Severity:** {High/Medium/Low}
-
-### Issue 2: {Title}
-...
-
-**Recommendation:**
-Consider running `/doc:feature` to update the documentation for this area before proceeding.
-
-**Can I still work?**
-{Yes/No} - {explanation of whether the task can proceed despite issues}
-```
-
----
-
-## Additional Guidelines
-
-### If No Input Provided
-
-If `{{{ input }}}` is empty or unclear:
-1. Read only `core/docs/01-fundamentals/` (general overview)
-2. Ask the user what specific area they want to work on
-3. Provide a list of available documentation topics
-
-### Theme-Specific Reading
-
-When working on theme-specific features, also read:
-- `contents/themes/{active-theme}/config/` - Theme configuration files
-- `contents/themes/{active-theme}/README.md` - Theme-specific docs (if exists)
-- `contents/themes/{active-theme}/docs/` - Theme documentation (if exists)
-
-### Rules Files
-
-For implementation tasks, also reference relevant rules:
-- `.rules/core.md` - Core development rules
-- `.rules/testing.md` - Testing requirements
-- `.rules/components.md` - UI component standards
-- `.rules/api.md` - API development patterns
-- `.rules/auth.md` - Authentication patterns
-
----
-
-## Output Format
-
-```markdown
-## Documentation Context Report
-
-**Topic:** {topic from input}
-**Active Theme:** {from NEXT_PUBLIC_ACTIVE_THEME}
-**Status:** {Coherent / Ambiguities / Errors}
-
-### Documentation Read
-- {list of documentation files read}
-
-### Code Verified
-- {list of code files checked}
-
-### Key Learnings
-{Bullet points of important concepts}
-
-### {Status-specific section from Step 5}
-
-### Ready to Proceed
-{Yes/No with explanation}
-```