@brainfish-ai/devdoc 0.1.33 → 0.1.35

package/ai-agents/.claude/skills/generate-api-docs/SKILL.md

@@ -1,94 +0,0 @@
----
-name: generate-api-docs
-description: Generate API documentation pages from OpenAPI spec or code
----
-
-## Instructions
-
-1. Analyze the OpenAPI spec or API code
-2. Create documentation pages for:
-   - Introduction/Overview
-   - Authentication guide
-   - Error handling
-   - Rate limiting (if applicable)
-3. Update docs.json to include API reference tab
-
-## OpenAPI Tab Configuration
-
-```json
-{
-  "tab": "API Reference",
-  "type": "openapi",
-  "path": "/api-reference",
-  "spec": "api-reference/openapi.json",
-  "groups": [
-    {
-      "group": "Overview",
-      "pages": ["api-reference/introduction", "api-reference/authentication"]
-    }
-  ]
-}
-```
-
-## GraphQL Tab Configuration
-
-```json
-{
-  "tab": "GraphQL API",
-  "type": "graphql",
-  "path": "/graphql-api",
-  "schema": "api-reference/schema.graphql",
-  "endpoint": "https://api.example.com/graphql"
-}
-```
-
-## Generated Pages
-
-### api-reference/introduction.mdx
-```mdx
----
-title: "API Introduction"
-description: "Overview of the API"
----
-
-Brief overview of the API capabilities.
-
-## Base URL
-
-\`\`\`
-https://api.example.com/v1
-\`\`\`
-
-## Authentication
-
-All requests require authentication. See [Authentication](/api-reference/authentication).
-```
-
-### api-reference/authentication.mdx
-```mdx
----
-title: "Authentication"
-description: "How to authenticate API requests"
----
-
-<Tabs>
-  <Tab title="Bearer Token">
-    Include the token in the Authorization header:
-    \`\`\`bash
-    curl -H "Authorization: Bearer YOUR_TOKEN" https://api.example.com/v1/users
-    \`\`\`
-  </Tab>
-  <Tab title="API Key">
-    Include the API key in the header:
-    \`\`\`bash
-    curl -H "X-API-Key: YOUR_KEY" https://api.example.com/v1/users
-    \`\`\`
-  </Tab>
-</Tabs>
-```
-
-## After Generating
-
-1. Review and customize the generated content
-2. Add real examples from your API
-3. Update authentication details

package/ai-agents/.claude/skills/sync-docs/SKILL.md

@@ -1,146 +0,0 @@
----
-name: sync-docs
-description: Analyze existing documentation against codebase and identify/fix outdated content. Reads docType from docs.json config.
----
-
-## Instructions
-
-When syncing documentation with the codebase:
-
-### Step 0: Locate Source Code
-
-First, determine where the source code is relative to current directory:
-- If `docs.json` exists here → you're in docs folder, source code is in `../`
-- If `package.json` and `src/` exist here → you're at repo root
-- Check both current directory AND parent directory for source files
-
-### Step 1: Get Documentation Type from Config
-
-**Read `docs.json` and check for `docType` field:**
-
-```json
-{
-  "docType": "api"  // "internal" | "api" | "product"
-}
-```
-
-**If `docType` is set:** Use that value automatically.
-
-**If `docType` is NOT set, detect from structure:**
-- Has `architecture/`, `development/` → "internal"
-- Has `api-reference/`, `sdks/` → "api"  
-- Has `features/`, `tutorials/` → "product"
-
-**If still unclear, ask:**
-"What type of documentation is this?
-1. internal - for your team
-2. api - for developers using your product
-3. product - for end users"
-
-**After user answers, save to docs.json:**
-Add `"docType": "{choice}"` to docs.json so it's remembered.
-Tell user: "Saved docType to docs.json - you won't be asked again."
-
-### Step 2: Build Documentation Inventory
-
-Scan all MDX files and extract:
-- Documented functions, classes, components
-- Code examples and their imports
-- API endpoints referenced
-- Package versions mentioned
-- CLI commands documented
-
-### Step 2: Analyze Current Codebase
-
-Compare documentation against source code:
-- Check if documented functions still exist
-- Verify function signatures match (parameters, return types)
-- Confirm API endpoints are still valid
-- Check if package versions are current
-- Identify new exports not yet documented
-
-### Step 3: Generate Sync Report
-
-Output a report categorizing issues:
-
-```
-## Documentation Sync Report
-
-### Outdated (Breaking Changes)
-- `docs/api/users.mdx`: `createUser()` signature changed
-  - Documented: `createUser(name: string)`
-  - Current: `createUser(data: UserInput)`
-
-### Outdated (Minor Changes)  
-- `docs/quickstart.mdx`: Package version outdated
-  - Documented: `v1.2.0`
-  - Current: `v1.5.0`
-
-### Missing Documentation
-- `src/utils/validator.ts` - New export, not documented
-- `POST /api/v2/webhooks` - New endpoint, not documented
-
-### Up to Date
-- `docs/guides/authentication.mdx`
-- `docs/components/button.mdx`
-```
-
-### Step 4: Update Options
-
-Ask user preference:
-1. **Auto-fix all** - Update all outdated docs automatically
-2. **Interactive** - Review each change before applying
-3. **Report only** - Just show the report, don't change anything
-
-### Step 5: Apply Updates
-
-When updating:
-- Preserve existing prose and explanations
-- Update code examples to match current signatures
-- Add TODO markers for sections needing human review
-- Update version numbers
-- Add stubs for missing documentation
-
-## Detection Patterns
-
-| Documentation Pattern | Codebase Check |
-|----------------------|----------------|
-| `import { X } from 'pkg'` | Verify X is exported from pkg |
-| `function X(a, b)` | Check X signature in source |
-| `v1.2.3` version strings | Compare with package.json |
-| `POST /api/users` | Verify route exists |
-| `<Component prop={x}>` | Check component props interface |
-
-## Update Strategies
-
-### For Changed Function Signatures
-```mdx
-// Before (outdated)
-createUser(name: string, email: string)
-
-// After (updated)
-createUser(data: UserInput)
-// Where UserInput = { name: string, email: string, role?: string }
-```
-
-### For Removed Features
-```mdx
-<Warning>
-**Deprecated**: This feature was removed in v2.0. 
-See [migration guide](/guides/v2-migration) for alternatives.
-</Warning>
-```
-
-### For New Features (stub)
-```mdx
----
-title: "New Feature"
-description: "Description"
----
-
-{/* TODO: Document this feature */}
-
-## Overview
-
-Coming soon...
-```

package/ai-agents/.claude/skills/update-docs-json/SKILL.md

@@ -1,60 +0,0 @@
----
-name: update-docs-json
-description: Add new pages to docs.json navigation configuration
----
-
-## Instructions
-
-When updating docs.json:
-
-1. Read the current docs.json structure
-2. Identify the appropriate group for the new page
-3. Add the page path (without .mdx extension)
-4. Maintain consistent ordering (introductory pages first)
-
-## Navigation Structure
-
-```json
-{
-  "navigation": {
-    "tabs": [
-      {
-        "tab": "Tab Name",
-        "type": "docs",
-        "groups": [
-          {
-            "group": "Group Name",
-            "icon": "phosphor-icon-name",
-            "pages": ["page-path", "folder/page-path"]
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-## Page Path Format
-
-- Use relative paths from docs root
-- Omit the `.mdx` extension
-- Use forward slashes for nested paths
-- Examples: `"quickstart"`, `"guides/authentication"`
-
-## Common Icons (Phosphor)
-
-- `rocket-launch` - Getting started
-- `book-open` - Documentation
-- `terminal` - CLI/Commands
-- `gear` - Configuration
-- `code` - Development
-- `puzzle-piece` - Components
-- `key` - Authentication
-- `cloud-arrow-up` - Deployment
-
-## Best Practices
-
-1. Group related pages together
-2. Order pages from basic to advanced
-3. Use descriptive group names
-4. Keep navigation depth shallow (max 2 levels)

package/ai-agents/.cursor/rules/devdoc-sync.mdc

@@ -1,105 +0,0 @@
----
-description: Rules for syncing and updating documentation with codebase changes
-globs: ["**/*.mdx", "**/docs.json"]
----
-
-# Documentation Sync Rules
-
-When asked to sync, update, or check documentation:
-
-## Step 1: Locate Source Code
-
-- If `docs.json` exists here → source code is in `../`
-- If `package.json` + `src/` exist → you're at repo root
-- Check both current directory AND parent for source files
-
-## Step 2: Get Documentation Type from Config
-
-**Read `docs.json` for `docType` field:**
-
-```json
-{ "docType": "api" }  // "internal" | "api" | "product"
-```
-
-**If `docType` is set:** Use that value automatically.
-
-**If `docType` is NOT set, detect from structure:**
-- Has `architecture/`, `development/` → "internal"
-- Has `api-reference/`, `sdks/` → "api"
-- Has `features/`, `tutorials/` → "product"
-
-**If still unclear, ask:** "What type of documentation is this?"
-
-**After user answers, save to docs.json:**
-Add `"docType": "{choice}"` to docs.json.
-Tell user: "Saved docType to docs.json - you won't be asked again."
-
-## Step 3: Analysis Process
-
-1. Compare documented APIs against source code exports
-2. Verify code examples compile/run correctly
-3. Check version numbers match package.json
-4. Validate all internal links resolve
-5. Identify new features needing documentation
-
-## Type-Specific Checks
-
-### For docType: "internal"
-- Dev setup instructions still work
-- Architecture diagrams match current code
-- Internal tool versions are current
-
-### For docType: "api"
-- API endpoints match OpenAPI spec
-- Auth examples are correct
-- SDK versions are current
-- Error codes are complete
-
-### For docType: "product"
-- Screenshots match current UI
-- Feature descriptions are accurate
-- Tutorials still work
-
-## Common Outdated Patterns
-
-- Function signatures that changed
-- Removed or renamed exports
-- Changed configuration options
-- Updated CLI commands
-- New required parameters
-- Deprecated features still documented
-
-## Update Guidelines
-
-- Preserve existing explanations and prose
-- Only update technical details (code, signatures, versions)
-- Add TODO comments for sections needing human review
-- Create stubs for undocumented new features
-- Mark deprecated features with Warning callout
-
-## Update Patterns
-
-### Changed Signature
-Update the documented signature to match source.
-
-### Removed Feature
-Add deprecation warning:
-```mdx
-<Warning>
-This feature was removed in vX.X.
-</Warning>
-```
-
-### New Feature
-Create stub with TODO:
-```mdx
-{/* TODO: Document this feature */}
-```
-
-## Report Format
-
-When checking docs, report:
-- Outdated items (with specific file:line)
-- Missing documentation
-- Broken links
-- Up-to-date items (summary)