project-iris 0.0.1

package/src/iris_bundle/frameworks/iris-core/artifacts.yaml

@@ -0,0 +1,78 @@
+schemaVersion: 1
+artifacts:
+  - id: requirements
+    type: requirements
+    mode: template
+    required: true
+    input:
+      from: [goal, targetUsers, problem, valueProp, mvpScope, successCriteria]
+    out: memory-bank/intents/{intentId}/requirements.md
+    output:
+      template: |
+        ---
+        status: draft
+        ---
+        # Requirements
+
+        ## Goal
+        {{goal}}
+
+        ## Target Users
+        {{targetUsers}}
+
+        ## Problem
+        {{problem}}
+
+        ## Value Proposition
+        {{valueProp}}
+
+        ## Scope
+        {{mvpScope}}
+
+        ## Success Criteria
+        {{successCriteria}}
+
+  - id: system-context
+    type: context
+    mode: template
+    input:
+      from: [platforms, integrations, frontendStack, backendStack]
+    out: memory-bank/intents/{intentId}/system-context.md
+    output:
+      template: |
+        ---
+        status: draft
+        ---
+        # System Context
+
+        ## Platforms
+        {{platforms}}
+
+        ## Integrations
+        {{integrations}}
+
+        ## Tech Stack
+        - Frontend: {{frontendStack}}
+        - Backend: {{backendStack}}
+
+  - id: unit-list
+    type: planning
+    mode: template
+    input:
+      from: [goal, mvpScope]
+    out: memory-bank/intents/{intentId}/unit-list.md
+    output:
+      template: |
+        ---
+        status: draft
+        ---
+        # Unit List
+
+        Goal: {{goal}}
+        Scope: {{mvpScope}}
+
+        ## Units
+        - [ ] U001: TBD
+              summary: Define this unit
+        - [ ] U002: TBD
+              summary: Define this unit

package/src/iris_bundle/frameworks/iris-core/dev_release_guide.md

@@ -0,0 +1,324 @@
+# Development & Release Guide
+
+## Branch Structure
+
+```mermaid
+gitGraph
+    commit id: "initial"
+    branch dev
+    checkout dev
+    commit id: "feat: parser"
+    commit id: "fix: bug"
+    checkout main
+    merge dev id: "auto v0.1.0" tag: "v0.1.0"
+    checkout dev
+    commit id: "feat: new feature"
+    commit id: "fix: another bug"
+    checkout main
+    merge dev id: "auto v0.1.1" tag: "v0.1.1"
+```
+
+## Branches
+
+| Branch | Purpose |
+|--------|---------|
+| `dev` | Active development. Push freely. CI validates every push. |
+| `main` | Production. Merge here to deploy. Version auto-bumped from commits. |
+
+---
+
+## How Auto-Versioning Works
+
+Semantic-release reads your commit messages and determines the version:
+
+| Commit Prefix | Version Bump | Example |
+|---------------|--------------|---------|
+| `fix:` | Patch | 0.0.34 → 0.0.35 |
+| `feat:` | Minor | 0.0.34 → 0.1.0 |
+| `perf:` | Patch | 0.0.34 → 0.0.35 |
+| `chore:`, `docs:`, `style:` | No release | - |
+
+**Note:** Major versions (1.0.0, 2.0.0) are NOT auto-bumped. Edit `package.json` manually.
+
+```mermaid
+flowchart LR
+    A[Commit Message] --> B{Prefix?}
+    B -->|fix:| C[Patch +0.0.1]
+    B -->|feat:| D[Minor +0.1.0]
+    B -->|perf:| E[Patch +0.0.1]
+    B -->|chore: docs:| F[No Release]
+```
+
+---
+
+## Workflow Overview
+
+```mermaid
+flowchart LR
+    subgraph dev[dev branch]
+        D1[Code] --> D2[Commit with prefix]
+        D2 --> D3[Push]
+        D3 --> D4{CI}
+        D4 -->|Pass| D5[Ready]
+        D4 -->|Fail| D1
+    end
+
+    subgraph main[main branch]
+        M1[Merge from dev] --> M2{CI}
+        M2 -->|Pass| M3[semantic-release]
+        M3 --> M4[Auto version bump]
+        M4 --> M5[npm publish]
+        M5 --> M6[GitHub Release]
+    end
+
+    D5 --> M1
+```
+
+---
+
+## Daily Workflow
+
+### 1. Start New Work (Sync with main)
+
+```bash
+git checkout dev
+git fetch origin
+git rebase origin/main
+```
+
+This ensures dev has all changes from main before starting new work.
+
+### 2. Development
+
+```bash
+git checkout dev
+# ... make changes ...
+git add .
+git commit -m "feat: add new parser feature"
+git push
+```
+
+**Use these commit prefixes:**
+
+- `feat:` - New feature (bumps minor)
+- `fix:` - Bug fix (bumps patch)
+- `perf:` - Performance improvement (bumps patch)
+- `docs:` - Documentation only (no release)
+- `chore:` - Maintenance (no release)
+- `refactor:` - Code refactor (no release)
+
+**Major versions** require manual edit of `package.json`.
+
+CI runs automatically on push.
+
+### 3. Deploy
+
+```bash
+git checkout main
+git merge dev
+git push
+```
+
+This triggers:
+
+1. CI runs (lint, test, build)
+2. semantic-release analyzes commits
+3. Auto-bumps version based on commit prefixes
+4. Publishes to npm
+5. Creates GitHub release with changelog
+
+---
+
+## Release Flow
+
+```mermaid
+sequenceDiagram
+    participant Dev as Developer
+    participant DevB as dev branch
+    participant MainB as main branch
+    participant CI as GitHub Actions
+    participant SR as semantic-release
+    participant NPM as npm Registry
+    participant GH as GitHub Releases
+
+    Dev->>DevB: git commit -m "feat: new feature"
+    Dev->>DevB: git push
+    DevB->>CI: Run tests
+    CI-->>Dev: Tests pass
+    Dev->>MainB: git merge dev
+    Dev->>MainB: git push
+    MainB->>CI: Run tests
+    CI->>SR: Analyze commits
+    SR->>SR: Detect "feat:" → minor bump
+    SR->>SR: 0.0.32 → 0.1.0
+    SR->>NPM: npm publish v0.1.0
+    SR->>GH: Create release v0.1.0
+    SR->>MainB: Commit version bump
+    GH-->>Dev: Release notes generated
+```
+
+---
+
+## Quick Reference
+
+### Start New Work (Always Do This First)
+
+```bash
+git checkout dev
+git fetch origin
+git rebase origin/main
+```
+
+### Commit Examples
+
+```bash
+# Bug fix → patch release (0.0.34 → 0.0.35)
+git commit -m "fix: resolve memory leak in watcher"
+
+# New feature → minor release (0.0.34 → 0.1.0)
+git commit -m "feat: add YAML validation support"
+
+# Performance → patch release (0.0.34 → 0.0.35)
+git commit -m "perf: optimize file parsing"
+
+# No release
+git commit -m "docs: update README"
+git commit -m "chore: update dependencies"
+```
+
+**For major releases:** Manually edit `version` in `package.json` then push.
+
+### Deploy to Production
+
+```bash
+git checkout main
+git merge dev
+git push
+# → Auto version, publish, release
+```
+
+### Check CI Status
+
+```bash
+gh run list
+gh run watch
+```
+
+### View Published Version
+
+```bash
+npm view irismd version
+```
+
+---
+
+## CI/CD Pipeline
+
+```mermaid
+flowchart TD
+    subgraph trigger[Triggers]
+        T1[Push to dev]
+        T2[Push to main]
+    end
+
+    subgraph ci[CI Jobs]
+        C1[Lint] --> C2[Test]
+        C2 --> C3[Build]
+    end
+
+    subgraph cd[Release - main only]
+        CD1[semantic-release]
+        CD2[Analyze commits]
+        CD3[Bump version]
+        CD4[npm publish]
+        CD5[GitHub Release]
+        CD1 --> CD2 --> CD3 --> CD4 --> CD5
+    end
+
+    T1 --> ci
+    T2 --> ci
+    ci -->|main only| cd
+```
+
+### On Push to `dev`
+
+- Lint check
+- Run tests
+- Build validation
+
+### On Push to `main`
+
+- Lint check
+- Run tests
+- Build validation
+- **semantic-release:**
+  - Analyze commit messages since last release
+  - Determine version bump (patch/minor/major)
+  - Update package.json
+  - Publish to npm
+  - Create GitHub release with auto-generated changelog
+
+---
+
+## Secrets Required
+
+| Secret | Purpose | Where to Set |
+|--------|---------|--------------|
+| `NPM_TOKEN` | Publish to npm registry | GitHub → Settings → Secrets → Actions |
+
+### Generate NPM Token
+
+```bash
+npm login
+npm token create --read-only=false
+```
+
+Copy token to GitHub repository secrets.
+
+---
+
+## Troubleshooting
+
+```mermaid
+flowchart TD
+    A[Problem?] --> B{CI Failed on main?}
+    B -->|Yes| C[Fix on dev]
+    C --> D[Re-merge to main]
+
+    B -->|No| E{No release created?}
+    E -->|Yes| F[Check commit prefixes]
+    F --> G[Use fix: or feat:]
+
+    E -->|No| H{Publish failed?}
+    H -->|Yes| I[Check NPM_TOKEN secret]
+    I --> J[Re-run workflow]
+
+    H -->|No| K[Check workflow logs]
+```
+
+### No Release Created
+
+- Commits need `fix:` or `feat:` prefix
+- `chore:`, `docs:`, `style:` don't trigger releases
+- Check if commits are reachable from main
+
+### CI Failed on Main
+
+- Fix issues on dev, re-merge
+
+### Check Workflow Logs
+
+```bash
+gh run list --branch main
+gh run view <run-id> --log
+```
+
+---
+
+## Setup Checklist
+
+- [ ] Create `dev` branch: `git checkout -b dev`
+- [ ] Add `NPM_TOKEN` secret in GitHub repo settings
+- [ ] Run `npm install` in `src/` to install semantic-release
+- [ ] Push both branches
+- [ ] Start committing with `fix:` and `feat:` prefixes

package/src/iris_bundle/frameworks/iris-core/docs.iris.md/.claude/skills/frontend-design/SKILL.md

@@ -0,0 +1,106 @@
+---
+name: frontend-design
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
+license: Complete terms in LICENSE.txt
+---
+
+This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
+
+The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
+
+## Design Thinking
+
+Before coding, understand the context and commit to a BOLD aesthetic direction:
+- **Purpose**: What problem does this interface solve? Who uses it?
+- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
+- **Constraints**: Technical requirements (framework, performance, accessibility).
+- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
+
+Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
+- Production-grade and functional
+- Visually striking and memorable
+- Cohesive with a clear aesthetic point-of-view
+- Meticulously refined in every detail
+
+## Frontend Aesthetics Guidelines
+
+Focus on:
+- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
+- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant color with intentional accents. Consider gradients, but make them subtle and purposeful.
+- **Spacing & Layout**: Generous whitespace creates luxury. Use CSS Grid and Flexbox for sophisticated layouts. Consider asymmetry for visual interest.
+- **Micro-interactions**: Thoughtful hover states, transitions, and animations. Make interactions feel alive but not overwhelming. 200-400ms transitions feel natural.
+- **Visual Details**: Subtle shadows, borders, and textures add depth. Consider backdrop-blur for modern glass effects. Rounded corners should be consistent throughout.
+- **Responsive Design**: Mobile-first approach. Breakpoints at 640px, 768px, 1024px, 1280px. Touch targets minimum 44px.
+
+## Implementation Patterns
+
+### CSS Architecture
+```css
+:root {
+  /* Colors */
+  --color-primary: #...;
+  --color-secondary: #...;
+  --color-background: #...;
+  --color-surface: #...;
+  --color-text: #...;
+  --color-text-muted: #...;
+
+  /* Typography */
+  --font-display: '...', serif;
+  --font-body: '...', sans-serif;
+  --font-mono: '...', monospace;
+
+  /* Spacing */
+  --space-xs: 0.25rem;
+  --space-sm: 0.5rem;
+  --space-md: 1rem;
+  --space-lg: 2rem;
+  --space-xl: 4rem;
+
+  /* Effects */
+  --radius-sm: 4px;
+  --radius-md: 8px;
+  --radius-lg: 16px;
+  --shadow-sm: 0 1px 2px rgba(0,0,0,0.05);
+  --shadow-md: 0 4px 6px rgba(0,0,0,0.1);
+  --shadow-lg: 0 10px 15px rgba(0,0,0,0.1);
+  --transition: 200ms ease;
+}
+```
+
+### Animation Principles
+- Entrance animations: fade + slight translate (20px max)
+- Hover states: scale(1.02-1.05), color shifts, shadow elevation
+- Loading states: skeleton screens over spinners
+- Scroll animations: intersection observer, staggered reveals
+
+### Accessibility
+- Semantic HTML elements
+- ARIA labels where needed
+- Focus states visible and styled
+- Color contrast ratios (4.5:1 minimum)
+- Reduced motion preference respected
+
+## Quality Checklist
+
+Before completion, verify:
+- [ ] Distinctive visual identity (not generic)
+- [ ] Consistent design system applied
+- [ ] Responsive across breakpoints
+- [ ] Smooth interactions and transitions
+- [ ] Accessible (keyboard, screen reader)
+- [ ] Performance optimized (no layout shifts)
+- [ ] Cross-browser compatible
+- [ ] Dark mode support (if applicable)
+
+## Output Format
+
+Deliver complete, production-ready code:
+1. HTML structure (semantic, accessible)
+2. CSS (organized, using variables)
+3. JavaScript (if interactive elements needed)
+4. Usage instructions if complex
+
+Focus on quality over quantity. A beautifully crafted component is better than a feature-complete but generic one.

package/src/iris_bundle/frameworks/iris-core/docs.iris.md/CLAUDE.md

@@ -0,0 +1,171 @@
+# iris.md Documentation Website
+
+This is the documentation website for [iris.md](https://github.com/fabriqaai/irismd), an AI-native software development framework with multi-agent orchestration.
+
+## Tech Stack
+
+- **Framework**: [Mintlify](https://mintlify.com) - Modern documentation platform
+- **Content**: MDX (Markdown + JSX)
+- **Diagrams**: Mermaid.js for flowcharts and diagrams
+- **Hosting**: Mintlify Cloud
+
+## Project Structure
+
+```
+iris.md-website/
+├── docs.json                 # Mintlify configuration (navigation, theme, etc.)
+├── index.mdx                 # Homepage
+├── faq.mdx                   # FAQ page
+├── getting-started/          # Getting started guides
+│   ├── installation.mdx
+│   └── quick-start.mdx
+├── methodology/              # AI-DLC methodology docs
+│   ├── what-is-ai-dlc.mdx
+│   ├── ai-dlc-vs-agile.mdx
+│   └── three-phases.mdx
+├── core-concepts/            # Core concepts
+│   ├── intents.mdx
+│   ├── units.mdx
+│   ├── bolts.mdx
+│   ├── memory-bank.mdx
+│   └── standards.mdx
+├── agents/                   # Agent documentation
+│   ├── overview.mdx
+│   ├── master-agent.mdx
+│   ├── inception-agent.mdx
+│   ├── construction-agent.mdx
+│   └── operations-agent.mdx
+├── architecture/             # Architecture docs
+│   └── flows.mdx
+├── guides/                   # How-to guides
+│   └── bolt-types.mdx
+└── images/                   # Static assets
+    ├── logo.png
+    ├── favicon.png
+    ├── hero-dark.svg
+    └── hero-light.svg
+```
+
+## Running Locally
+
+```bash
+# Install Mintlify CLI
+npm i -g mintlify
+
+# Start dev server
+npx mint dev
+```
+
+The site will be available at http://localhost:3000
+
+## Navigation Configuration
+
+Navigation is configured in `docs.json`. The structure uses nested groups:
+
+- **Getting Started**: Installation and quick start
+- **Framework**: Architecture overview
+- **AI-DLC Flow**: The main methodology section
+  - Concepts (Intents, Units, Bolts, Memory Bank, Standards)
+  - Agents (Master, Inception, Construction, Operations)
+  - Guides
+
+## Writing Content
+
+### MDX Components
+
+Mintlify provides built-in components:
+
+```mdx
+<Info>Informational callout</Info>
+<Warning>Warning callout</Warning>
+<Card title="Title" icon="icon-name" href="/path">Description</Card>
+<CardGroup cols={2}>...</CardGroup>
+<Tabs><Tab title="Tab 1">...</Tab></Tabs>
+<Steps><Step title="Step 1">...</Step></Steps>
+<AccordionGroup><Accordion title="Title">...</Accordion></AccordionGroup>
+```
+
+### Frontmatter
+
+Every MDX file needs frontmatter:
+
+```yaml
+---
+title: Page Title
+description: Brief description for SEO
+---
+```
+
+## Mermaid Diagram Theme
+
+Use consistent styling for all Mermaid diagrams. Copy these styles into your diagrams.
+
+### Color Palette
+
+| Role               | Color  | Hex       | Usage                         |
+|--------------------|--------|-----------|-------------------------------|
+| Master/Primary     | Purple | `#8B5CF6` | Master Agent, primary elements |
+| Inception          | Indigo | `#818CF8` | Inception phase, planning     |
+| Construction       | Green  | `#34D399` | Construction phase, building  |
+| Operations         | Amber  | `#FBBF24` | Operations phase, deployment  |
+| Human/Validation   | Pink   | `#F472B6` | Human review, checkpoints     |
+| AI/System          | Cyan   | `#22D3EE` | AI actions, automation        |
+| Core/Infrastructure| Blue   | `#60A5FA` | Core components               |
+| Future/Placeholder | Gray   | `#64748B` | Planned features              |
+
+### Standard Style Definitions
+
+**Agent Flow Diagram:**
+```
+style MA fill:#8B5CF6,stroke:#7C3AED,color:#fff
+style IA fill:#818CF8,stroke:#6366F1,color:#fff
+style CA fill:#34D399,stroke:#10B981,color:#fff
+style OA fill:#FBBF24,stroke:#F59E0B,color:#fff
+```
+
+**Human Checkpoints Diagram:**
+```
+style Stage fill:#818CF8,stroke:#6366F1,color:#fff
+style Gate fill:#F472B6,stroke:#EC4899,color:#fff
+```
+
+**Role Comparison (Human vs AI):**
+```
+style Human fill:#60A5FA,stroke:#3B82F6,color:#fff
+style AI fill:#34D399,stroke:#10B981,color:#fff
+style Validate fill:#F472B6,stroke:#EC4899,color:#fff
+```
+
+**Framework Architecture:**
+```
+style Framework fill:#1E293B,stroke:#334155,color:#fff
+style Core fill:#0C4A6E,stroke:#0EA5E9,color:#fff
+style Flows fill:#052E16,stroke:#22C55E,color:#fff
+style Active fill:#22C55E,stroke:#16A34A,color:#fff
+style Future fill:#475569,stroke:#64748B,color:#fff,stroke-dasharray: 5 5
+```
+
+**Bolt Types:**
+```
+style DDD fill:#8B5CF6,stroke:#7C3AED,color:#fff
+style Simple fill:#34D399,stroke:#10B981,color:#fff
+style Spike fill:#FBBF24,stroke:#F59E0B,color:#fff
+```
+
+## Brand Colors
+
+From `docs.json`:
+- Primary: `#CD6B4D` (terracotta/rust)
+- Light: `#D17A5E`
+- Dark: `#B85A3D`
+
+## Important Notes
+
+1. **Agent commands are NOT CLI commands** - They are prompts typed in AI coding tools (Claude Code, Cursor, GitHub Copilot)
+2. **ASCII file trees should stay as ASCII** - They represent directory structures and are more readable than Mermaid
+3. **Process flows should use Mermaid** - Flowcharts, state diagrams, and architecture diagrams
+4. **Always include frontmatter** - Title and description are required for SEO
+
+## Related Repositories
+
+- Main iris.md CLI: https://github.com/fabriqaai/irismd

package/src/iris_bundle/frameworks/iris-core/docs.iris.md/README.md

@@ -0,0 +1,20 @@
+# iris.md-website
+
+This is the documentation website for iris.md, built with **Mintlify**.
+
+## Getting Started
+
+1.  Install Mintlify CLI:
+    ```bash
+    npm i -g mintlify
+    ```
+
+2.  Run the development server:
+    ```bash
+    mintlify dev
+    ```
+
+## Structure
+
+-   `mint.json`: Configuration (Navigation, Colors, Branding).
+-   `introduction.mdx`: Main content page.