skillstore-cli 1.0.0

package/data/free-skills/devflow-bootstrap/plugin/skills/project-scaffold/references/stack-templates.md

@@ -0,0 +1,400 @@
+# Stack Templates
+
+## Next.js (App Router)
+
+```
+project-root/
+├── src/
+│   ├── app/
+│   │   ├── layout.tsx
+│   │   ├── page.tsx
+│   │   ├── globals.css
+│   │   ├── (auth)/
+│   │   │   ├── login/page.tsx
+│   │   │   └── register/page.tsx
+│   │   └── api/
+│   │       └── health/route.ts
+│   ├── components/
+│   │   ├── ui/           # Reusable UI components (Button, Input, Modal...)
+│   │   ├── layout/       # Header, Footer, Sidebar, Navigation
+│   │   └── features/     # Feature-specific components
+│   ├── lib/
+│   │   ├── utils.ts
+│   │   ├── constants.ts
+│   │   └── validations.ts
+│   ├── hooks/
+│   │   └── index.ts
+│   ├── services/         # API client, external service integrations
+│   │   └── api.ts
+│   ├── stores/           # State management (Zustand/Jotai)
+│   │   └── index.ts
+│   └── types/
+│       └── index.ts
+├── public/
+│   └── assets/
+├── tests/
+│   ├── unit/
+│   └── e2e/
+├── next.config.ts
+├── tsconfig.json
+├── tailwind.config.ts
+├── postcss.config.mjs
+├── package.json
+├── .env.example
+├── .gitignore
+└── README.md
+```
+
+**Key configs:**
+- `tsconfig.json`: strict mode, path aliases (`@/*` → `src/*`)
+- `tailwind.config.ts`: content paths, custom theme extensions
+- `next.config.ts`: image domains, redirects, env exposure
+
+---
+
+## NestJS
+
+```
+project-root/
+├── src/
+│   ├── main.ts
+│   ├── app.module.ts
+│   ├── app.controller.ts
+│   ├── app.service.ts
+│   ├── common/
+│   │   ├── decorators/
+│   │   ├── filters/
+│   │   │   └── http-exception.filter.ts
+│   │   ├── guards/
+│   │   │   └── auth.guard.ts
+│   │   ├── interceptors/
+│   │   │   └── logging.interceptor.ts
+│   │   ├── middleware/
+│   │   ├── pipes/
+│   │   │   └── validation.pipe.ts
+│   │   └── interfaces/
+│   ├── config/
+│   │   ├── configuration.ts
+│   │   └── validation.ts
+│   ├── modules/
+│   │   ├── auth/
+│   │   │   ├── auth.module.ts
+│   │   │   ├── auth.controller.ts
+│   │   │   ├── auth.service.ts
+│   │   │   ├── dto/
+│   │   │   ├── guards/
+│   │   │   └── strategies/
+│   │   └── users/
+│   │       ├── users.module.ts
+│   │       ├── users.controller.ts
+│   │       ├── users.service.ts
+│   │       ├── dto/
+│   │       ├── entities/
+│   │       └── users.repository.ts
+│   └── database/
+│       ├── database.module.ts
+│       └── migrations/
+├── test/
+│   ├── app.e2e-spec.ts
+│   └── jest-e2e.json
+├── nest-cli.json
+├── tsconfig.json
+├── tsconfig.build.json
+├── package.json
+├── .env.example
+├── .gitignore
+└── README.md
+```
+
+**Key configs:**
+- `nest-cli.json`: compiler options, asset handling
+- `tsconfig.json`: decorator metadata, strict mode
+- Validation via `class-validator` + `class-transformer`
+
+---
+
+## Spring Boot
+
+```
+project-root/
+├── src/
+│   ├── main/
+│   │   ├── java/com/example/project/
+│   │   │   ├── Application.java
+│   │   │   ├── config/
+│   │   │   │   ├── SecurityConfig.java
+│   │   │   │   └── WebConfig.java
+│   │   │   ├── controller/
+│   │   │   │   └── HealthController.java
+│   │   │   ├── service/
+│   │   │   │   └── impl/
+│   │   │   ├── repository/
+│   │   │   ├── model/
+│   │   │   │   ├── entity/
+│   │   │   │   ├── dto/
+│   │   │   │   └── mapper/
+│   │   │   ├── exception/
+│   │   │   │   ├── GlobalExceptionHandler.java
+│   │   │   │   └── ResourceNotFoundException.java
+│   │   │   └── util/
+│   │   └── resources/
+│   │       ├── application.yml
+│   │       ├── application-dev.yml
+│   │       ├── application-staging.yml
+│   │       ├── application-prod.yml
+│   │       └── db/migration/      # Flyway migrations
+│   └── test/
+│       └── java/com/example/project/
+│           ├── controller/
+│           └── service/
+├── pom.xml                         # or build.gradle.kts
+├── .env.example
+├── .gitignore
+├── Dockerfile
+└── README.md
+```
+
+**Key configs:**
+- Maven: `pom.xml` with Spring Boot parent, dependencies (Web, JPA, Security, Validation)
+- Gradle: `build.gradle.kts` with plugins, dependencies
+- Profile-based config: `application-{env}.yml`
+
+---
+
+## Express + TypeScript
+
+```
+project-root/
+├── src/
+│   ├── index.ts
+│   ├── app.ts
+│   ├── config/
+│   │   ├── index.ts
+│   │   └── database.ts
+│   ├── routes/
+│   │   ├── index.ts
+│   │   └── health.route.ts
+│   ├── controllers/
+│   │   └── health.controller.ts
+│   ├── services/
+│   ├── models/
+│   ├── middleware/
+│   │   ├── error-handler.ts
+│   │   ├── auth.ts
+│   │   ├── validation.ts
+│   │   └── logger.ts
+│   ├── utils/
+│   │   └── logger.ts
+│   └── types/
+│       └── index.ts
+├── tests/
+│   ├── unit/
+│   └── integration/
+├── tsconfig.json
+├── package.json
+├── .env.example
+├── .gitignore
+├── Dockerfile
+└── README.md
+```
+
+**Key configs:**
+- `tsconfig.json`: outDir, rootDir, strict, path aliases
+- Express setup: CORS, helmet, compression, rate limiting
+- Error handling: centralized error handler middleware
+
+---
+
+## React + Vite
+
+```
+project-root/
+├── src/
+│   ├── main.tsx
+│   ├── App.tsx
+│   ├── components/
+│   │   ├── ui/
+│   │   ├── layout/
+│   │   └── features/
+│   ├── pages/
+│   ├── hooks/
+│   ├── stores/            # Zustand / Redux Toolkit
+│   ├── services/
+│   │   └── api.ts
+│   ├── utils/
+│   ├── types/
+│   ├── styles/
+│   │   └── globals.css
+│   └── assets/
+├── public/
+├── tests/
+│   ├── unit/
+│   └── e2e/
+├── vite.config.ts
+├── tsconfig.json
+├── tsconfig.node.json
+├── index.html
+├── package.json
+├── .env.example
+├── .gitignore
+└── README.md
+```
+
+**Key configs:**
+- `vite.config.ts`: plugins (react), resolve aliases, proxy
+- `tsconfig.json`: JSX, path aliases, strict
+- Test setup: Vitest + React Testing Library
+
+---
+
+## Python FastAPI
+
+```
+project-root/
+├── app/
+│   ├── __init__.py
+│   ├── main.py
+│   ├── config.py
+│   ├── dependencies.py
+│   ├── routers/
+│   │   ├── __init__.py
+│   │   └── health.py
+│   ├── models/
+│   │   ├── __init__.py
+│   │   └── base.py
+│   ├── schemas/
+│   │   └── __init__.py
+│   ├── services/
+│   │   └── __init__.py
+│   ├── repositories/
+│   │   └── __init__.py
+│   └── utils/
+│       └── __init__.py
+├── tests/
+│   ├── conftest.py
+│   ├── test_health.py
+│   └── factories/
+├── alembic/
+│   ├── env.py
+│   └── versions/
+├── alembic.ini
+├── pyproject.toml
+├── requirements.txt
+├── .env.example
+├── .gitignore
+├── Dockerfile
+└── README.md
+```
+
+**Key configs:**
+- `pyproject.toml`: project metadata, dependencies, tool configs (ruff, mypy, pytest)
+- Alembic for database migrations
+- Pydantic settings for config management
+
+---
+
+## Flutter
+
+```
+project-root/
+├── lib/
+│   ├── main.dart
+│   ├── app.dart
+│   ├── core/
+│   │   ├── constants/
+│   │   ├── theme/
+│   │   ├── utils/
+│   │   └── network/
+│   │       └── api_client.dart
+│   ├── features/
+│   │   ├── auth/
+│   │   │   ├── data/
+│   │   │   ├── domain/
+│   │   │   └── presentation/
+│   │   └── home/
+│   │       ├── data/
+│   │       ├── domain/
+│   │       └── presentation/
+│   ├── models/
+│   ├── services/
+│   └── widgets/           # Shared widgets
+├── test/
+│   ├── unit/
+│   ├── widget/
+│   └── integration/
+├── assets/
+│   ├── images/
+│   ├── fonts/
+│   └── icons/
+├── pubspec.yaml
+├── analysis_options.yaml
+├── .env.example
+├── .gitignore
+└── README.md
+```
+
+**Key configs:**
+- `pubspec.yaml`: dependencies (riverpod/bloc, dio, freezed, go_router)
+- `analysis_options.yaml`: strict lint rules
+- Feature-based architecture (clean architecture pattern)
+
+---
+
+## Monorepo (Turborepo / Nx)
+
+```
+project-root/
+├── apps/
+│   ├── web/               # Next.js or React app
+│   ├── api/               # NestJS or Express backend
+│   ├── mobile/            # React Native or Flutter
+│   └── admin/             # Admin dashboard
+├── packages/
+│   ├── ui/                # Shared UI component library
+│   ├── config-eslint/     # Shared ESLint config
+│   ├── config-typescript/ # Shared TypeScript config
+│   ├── utils/             # Shared utilities
+│   └── types/             # Shared type definitions
+├── turbo.json             # or nx.json
+├── package.json           # Root workspace config
+├── pnpm-workspace.yaml    # or npm/yarn workspaces
+├── tsconfig.base.json
+├── .env.example
+├── .gitignore
+├── Dockerfile
+└── README.md
+```
+
+**Key configs:**
+- `turbo.json`: pipeline definitions (build, lint, test, dev)
+- Root `package.json`: workspace definition, shared scripts
+- Shared configs: ESLint, TypeScript, Prettier inherited by all packages
+
+---
+
+## Common Files (All Stacks)
+
+### .gitignore
+- Node: `node_modules/`, `.next/`, `dist/`, `.env`, `.env.local`
+- Python: `__pycache__/`, `.venv/`, `*.pyc`, `.env`
+- Java: `target/`, `build/`, `.gradle/`, `*.class`
+- General: `.DS_Store`, `*.log`, `.idea/`, `.vscode/` (except shared settings)
+
+### README.md Template
+- Project name + description
+- Prerequisites
+- Getting started (install, setup env, run dev)
+- Available scripts/commands
+- Project structure overview
+- Contributing guidelines link
+
+### .env.example
+- All required environment variables with placeholder values
+- Grouped by category (App, Database, Auth, External Services)
+- Comments explaining each variable
+
+### docker-compose.yml
+- App service (with Dockerfile)
+- Database service (PostgreSQL/MySQL/MongoDB)
+- Cache service (Redis) if needed
+- Network and volume definitions

package/data/free-skills/devflow-bootstrap/template/agents/bootstrap-specialist.md

@@ -0,0 +1,56 @@
+---
+name: bootstrap-specialist
+description: Use this agent to orchestrate Sprint 0 project setup — scaffolding, CI/CD, environment configuration, and code standards. Coordinates all bootstrap skills for end-to-end project initialization.
+tools: Glob, Grep, LS, Read, Edit, Write, Bash
+---
+
+You are a DevOps & Project Setup Specialist with deep expertise in modern development toolchains. You turn project requirements into fully configured, CI/CD-ready codebases.
+
+## Core Responsibilities
+
+### 1. Project Scaffolding
+- Activate `project-scaffold` skill
+- Generate directory structure and boilerplate for selected tech stack
+- Configure package manager, path aliases, module resolution
+- Create README, .gitignore, .env.example
+
+### 2. CI/CD Pipeline Setup
+- Activate `cicd-setup` skill
+- Generate workflow files for target platform (GitHub Actions, GitLab CI, Jenkins)
+- Configure stages: lint → test → build → deploy
+- Set up environment-specific deployments (preview, staging, production)
+
+### 3. Environment Configuration
+- Activate `env-configurator` skill
+- Generate .env templates for each environment
+- Configure Docker Compose for local development
+- Set up environment variable validation
+
+### 4. Code Standards
+- Activate `code-standards-init` skill
+- Install and configure linters, formatters, git hooks
+- Set up conventional commit enforcement
+- Configure editor settings
+
+## Execution Order
+
+```
+1. project-scaffold  (foundation)
+2. code-standards-init  (quality tooling on top of scaffold)
+3. env-configurator  (environment setup)
+4. cicd-setup  (pipeline references the project structure)
+```
+
+Steps 2 and 3 can run in parallel after step 1.
+
+## Error Recovery
+- If tech stack ambiguous: ask user to confirm before scaffolding
+- If package install fails: retry once, then report with error log
+- If config conflicts detected: report both options, let user decide
+- Max retries: 2 per skill activation
+
+## Checkpoint Protocol
+After completing each skill activation:
+1. Save generated files list
+2. Log: skill name, files created, warnings encountered
+3. If interrupted: resume from last completed skill

package/data/free-skills/devflow-bootstrap/template/workflows/bootstrap-workflow.md

@@ -0,0 +1,70 @@
+# Bootstrap Workflow
+
+End-to-end Sprint 0 project setup from tech stack decision to production-ready codebase.
+
+## Phase 1: Discovery
+
+1. **Requirements Gathering**
+   - Identify tech stack (language, framework, database)
+   - Determine deployment target (Vercel, AWS, GCP, self-hosted)
+   - List integrations needed (auth, payments, email, analytics)
+   - Define team size and branching strategy
+
+2. **Stack Validation**
+   - `bootstrap-specialist` validates compatibility of chosen technologies
+   - Flag potential conflicts (e.g., incompatible library versions)
+   - Confirm monorepo vs single-project structure
+   - Output: Validated tech stack document
+
+## Phase 2: Foundation
+
+3. **Project Scaffolding**
+   - `bootstrap-specialist` activates `project-scaffold` skill
+   - Generate directory structure from stack template
+   - Create boilerplate files (entry points, configs, types)
+   - Output: Project structure with README and .gitignore
+
+4. **Code Standards** (parallel with step 5)
+   - `bootstrap-specialist` activates `code-standards-init` skill
+   - Install linter, formatter, git hooks
+   - Configure commit message enforcement
+   - Output: Quality tooling configured and verified
+
+5. **Environment Setup** (parallel with step 4)
+   - `bootstrap-specialist` activates `env-configurator` skill
+   - Generate .env templates per environment
+   - Configure Docker Compose for local development
+   - Set up environment variable validation
+   - Output: Environment configs and Docker setup
+
+## Phase 3: Pipeline
+
+6. **CI/CD Configuration**
+   - `bootstrap-specialist` activates `cicd-setup` skill
+   - Input: Project structure from phase 2
+   - Generate workflow files (lint → test → build → deploy)
+   - Configure environment-specific deployments
+   - Output: CI/CD pipeline files
+
+## Phase 4: Verification
+
+7. **End-to-End Check**
+   - Verify all config files have valid syntax
+   - Run linter to confirm zero errors on clean project
+   - Run formatter to confirm no changes needed
+   - Verify git hooks execute correctly
+   - Confirm CI workflow is syntactically valid
+   - Output: Verification report
+
+8. **Handoff**
+   - Present generated file tree to user
+   - List required secrets and environment variables
+   - Provide getting-started instructions
+   - Suggest first sprint backlog items
+
+## Quality Gates
+
+- **After Phase 1**: Tech stack confirmed by user
+- **After Phase 2**: `pnpm lint` and `pnpm format:check` pass with zero errors
+- **After Phase 3**: CI workflow validated (YAML syntax + logical correctness)
+- **After Phase 4**: User confirms setup meets requirements

package/data/free-skills/devflow-docs/manifest.json

@@ -0,0 +1,8 @@
+{
+  "name": "@skillstore/devflow-docs",
+  "version": "1.0.0",
+  "skills": ["pdf-processor", "excel-analyzer", "doc-generator", "presentation-reviewer"],
+  "freeSkills": ["pdf-processor"],
+  "commands": ["docs", "docs/parse", "docs/generate"],
+  "modes": ["plugin", "template"]
+}

package/data/free-skills/devflow-docs/plugin/commands/devflow.md

@@ -0,0 +1,20 @@
+---
+description: DevFlow smart router — automatically routes to the right DevFlow package
+argument-hint: [task description]
+---
+
+## Smart Routing
+
+<task>
+$ARGUMENTS
+</task>
+
+Analyze the task and route to the appropriate DevFlow command:
+
+| Keywords/Context | Route To |
+|------------------|----------|
+| PDF, Excel, document, parse, generate report, PowerPoint | `/docs` |
+| presale, RFP, proposal, estimate, pricing | `/presale` |
+| sprint, standup, agile, backlog, scrum | `/agile` |
+| handover, maintenance, retrospective, post-project | `/postproject` |
+| scaffold, setup, init, Sprint 0, CI/CD, environment | `/bootstrap` |

package/data/free-skills/devflow-docs/plugin/commands/docs/generate.md

@@ -0,0 +1,17 @@
+---
+description: Generate a professional document from data or analysis
+argument-hint: [document type and content/data]
+---
+
+## Your Mission
+
+<input>
+$ARGUMENTS
+</input>
+
+## Process
+1. Activate `doc-generator` skill
+2. Identify document type (report, proposal, handover, status)
+3. Select appropriate template
+4. Assemble content from provided data
+5. Format and output complete document

package/data/free-skills/devflow-docs/plugin/commands/docs/parse.md

@@ -0,0 +1,19 @@
+---
+description: Parse and extract content from a document (PDF, Excel, PowerPoint)
+argument-hint: [file path or paste content]
+---
+
+## Your Mission
+
+<input>
+$ARGUMENTS
+</input>
+
+## Process
+1. Identify document type (PDF, Excel, PowerPoint, Word)
+2. Route to appropriate skill:
+   - PDF → `pdf-processor`
+   - Excel/CSV → `excel-analyzer`
+   - PowerPoint → `presentation-reviewer`
+3. Extract structured content
+4. Output in clean Markdown format

package/data/free-skills/devflow-docs/plugin/commands/docs.md

@@ -0,0 +1,26 @@
+---
+description: Document processing — parse, analyze, and generate documents
+argument-hint: [task or file reference]
+---
+
+## Your Mission
+
+<task>
+$ARGUMENTS
+</task>
+
+## Smart Routing
+
+| Keywords/Patterns | Route To |
+|-------------------|----------|
+| PDF, RFP, contract, spec (read) | `pdf-processor` skill |
+| Excel, CSV, budget, resource plan, data | `excel-analyzer` skill |
+| Generate, create, report, template (write) | `doc-generator` skill |
+| PowerPoint, slides, presentation, deck | `presentation-reviewer` skill |
+
+## Sub-commands
+- `/docs:parse [file]` — Extract content from any document type
+- `/docs:generate [template]` — Generate document from data/analysis
+
+## References
+- `protocols/error-recovery.md` for failure handling

package/data/free-skills/devflow-docs/plugin/skills/pdf-processor/SKILL.md

@@ -0,0 +1,59 @@
+# PDF Processor
+
+Process PDF documents: extract text, tables, forms, images. Use for RFP analysis, contract review, spec extraction.
+
+## Triggers
+
+- Received PDF from client
+- Need to extract requirements from RFP
+- Contract review
+- Spec analysis
+- Any PDF document that needs structured data extraction
+
+## Process
+
+```
+Document Assessment → Content Extraction → Structure Recognition → Data Transformation → Output
+```
+
+### Step 1: Document Assessment
+- Determine PDF type: native text vs scanned (image-based)
+- Check page count and document structure
+- Identify language(s) used
+- Assess quality (resolution, readability)
+
+### Step 2: Content Extraction
+- Extract raw text using appropriate method (native text extraction or OCR)
+- Identify and extract tables
+- Extract form fields and their values
+- Extract embedded images and diagrams
+- Pull metadata (author, creation date, version, title)
+
+### Step 3: Structure Recognition
+- Detect document sections (headings, subheadings)
+- Map table of contents to content
+- Identify lists, bullet points, numbered items
+- Recognize header/footer patterns
+- Detect multi-column layouts
+
+### Step 4: Data Transformation
+- Convert tables to structured format (Markdown tables or JSON)
+- Organize extracted text by sections
+- Link images/diagrams to relevant sections
+- Normalize data formats (dates, currency, percentages)
+
+### Step 5: Output
+- Deliver extracted content in clean Markdown
+- Include confidence scores for OCR-based extractions
+- Flag sections with low extraction quality
+- Provide summary of document structure
+
+## References
+- `references/extraction-techniques.md` — Detailed extraction strategies
+- `assets/sample-output.md` — Example extraction output
+
+## Notes
+- For scanned PDFs, extraction quality depends on scan resolution
+- Multi-language documents may require language detection per section
+- Always validate table extraction against visual layout
+- Large PDFs (100+ pages): process in chunks, report progress