feat: add initial specification and quality checklist for Real-Time C…

.claude/commands/speckit.analyze.md

@@ -1,4 +1,8 @@
 ---
+# SPDX-FileCopyrightText: 2026 Github
+#
+# SPDX-License-Identifier: MIT
+
 description: Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
 ---
 

.claude/commands/speckit.checklist.md

@@ -1,4 +1,8 @@
 ---
+# SPDX-FileCopyrightText: 2026 Github
+#
+# SPDX-License-Identifier: MIT
+
 description: Generate a custom checklist for the current feature based on user requirements.
 ---
 

.claude/commands/speckit.clarify.md

@@ -1,4 +1,8 @@
 ---
+# SPDX-FileCopyrightText: 2026 Github
+#
+# SPDX-License-Identifier: MIT
+
 description: Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
 handoffs: 
   - label: Build Technical Plan

.claude/commands/speckit.constitution.md

@@ -1,4 +1,8 @@
 ---
+# SPDX-FileCopyrightText: 2026 Github
+#
+# SPDX-License-Identifier: MIT
+
 description: Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
 handoffs: 
   - label: Build Specification

.claude/commands/speckit.implement.md

@@ -1,4 +1,8 @@
 ---
+# SPDX-FileCopyrightText: 2026 Github
+#
+# SPDX-License-Identifier: MIT
+
 description: Execute the implementation plan by processing and executing all tasks defined in tasks.md
 ---
 

.claude/commands/speckit.plan.md

@@ -1,4 +1,8 @@
 ---
+# SPDX-FileCopyrightText: 2026 Github
+#
+# SPDX-License-Identifier: MIT
+
 description: Execute the implementation planning workflow using the plan template to generate design artifacts.
 handoffs: 
   - label: Create Tasks

.claude/commands/speckit.specify.md

@@ -1,4 +1,8 @@
 ---
+# SPDX-FileCopyrightText: 2026 Github
+#
+# SPDX-License-Identifier: MIT
+
 description: Create or update the feature specification from a natural language feature description.
 handoffs: 
   - label: Build Technical Plan

.claude/commands/speckit.tasks.md

@@ -1,4 +1,8 @@
 ---
+# SPDX-FileCopyrightText: 2026 Github
+#
+# SPDX-License-Identifier: MIT
+
 description: Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
 handoffs: 
   - label: Analyze For Consistency

.claude/commands/speckit.taskstoissues.md

@@ -1,4 +1,8 @@
 ---
+# SPDX-FileCopyrightText: 2026 Github
+#
+# SPDX-License-Identifier: MIT
+
 description: Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
 tools: ['github/github-mcp-server/issue_write']
 ---

.claude/skills/cocoindex-rust/SKILL.md

@@ -1,4 +1,9 @@
 ---
+# SPDX-FileCopyrightText: 2026 Knitli Inc.
+# SPDX-FileContributor: Adam Poulemanos <adam@knit.li>
+#
+# SPDX-License-Identifier: AGPL-3.0-or-later
+
 name: cocoindex-rust
 description: Comprehensive toolkit for developing with the CocoIndex Rust API. Use when building high-performance operators, embedding the engine in Rust applications, or extending the core framework. Covers LibContext management, custom native operators, and direct execution control.
 ---

.claude/skills/cocoindex-rust/resources/api_function.md

@@ -1,3 +1,10 @@
+<!--
+SPDX-FileCopyrightText: 2026 Knitli Inc.
+SPDX-FileContributor: Adam Poulemanos <adam@knit.li>
+
+SPDX-License-Identifier: AGPL-3.0-or-later
+-->
+
 # CocoIndex Rust API: Functions
 
 Implement stateless transformations using `cocoindex::ops::interface`.

.claude/skills/cocoindex-rust/resources/api_setup.md

@@ -1,3 +1,10 @@
+<!--
+SPDX-FileCopyrightText: 2026 Knitli Inc.
+SPDX-FileContributor: Adam Poulemanos <adam@knit.li>
+
+SPDX-License-Identifier: AGPL-3.0-or-later
+-->
+
 # CocoIndex Rust API: Setup & Context
 
 Using `cocoindex::lib_context` and `cocoindex::settings`.

.claude/skills/cocoindex-rust/resources/api_source.md

@@ -1,3 +1,10 @@
+<!--
+SPDX-FileCopyrightText: 2026 Knitli Inc.
+SPDX-FileContributor: Adam Poulemanos <adam@knit.li>
+
+SPDX-License-Identifier: AGPL-3.0-or-later
+-->
+
 # CocoIndex Rust API: Sources
 
 Implement high-performance data sources using `cocoindex::ops::interface`.

.claude/skills/cocoindex-rust/resources/api_surface.md

@@ -1,3 +1,10 @@
+<!--
+SPDX-FileCopyrightText: 2026 Knitli Inc.
+SPDX-FileContributor: Adam Poulemanos <adam@knit.li>
+
+SPDX-License-Identifier: AGPL-3.0-or-later
+-->
+
 # CocoIndex Rust API Surface
 
 Based on analysis of the `cocoindex` crate (v0.1.0+).

.claude/skills/cocoindex-rust/resources/api_types.md

@@ -1,3 +1,10 @@
+<!--
+SPDX-FileCopyrightText: 2026 Knitli Inc.
+SPDX-FileContributor: Adam Poulemanos <adam@knit.li>
+
+SPDX-License-Identifier: AGPL-3.0-or-later
+-->
+
 # CocoIndex Rust API: Types
 
 The type system is defined in `cocoindex::base`.

.editorconfig

@@ -1,3 +1,8 @@
+# SPDX-FileCopyrightText: 2026 Knitli Inc.
+# SPDX-FileContributor: Adam Poulemanos <adam@knit.li>
+#
+# SPDX-License-Identifier: AGPL-3.0-or-later
+
 # EditorConfig is awesome: https://EditorConfig.org
 
 # top-most EditorConfig file

.gemini/commands/sc.agent.toml

@@ -0,0 +1,79 @@
+# SPDX-FileCopyrightText: 2026 SuperClaude-Org Contributors
+#
+# SPDX-License-Identifier: MIT
+
+description = "SC Agent — session controller that orchestrates investigation, implementation, and review"
+prompt = """
+name: sc:agent
+description: SC Agent — session controller that orchestrates investigation, implementation, and review
+category: orchestration
+personas: []
+---
+
+# SC Agent Activation
+
+🚀 **SC Agent online** — this plugin launches `/sc:agent` automatically at session start.
+
+## Startup Checklist (keep output terse)
+1. `git status --porcelain` → announce `📊 Git: clean|X files|not a repo`.
+2. Remind the user: `💡 Use /context to confirm token budget.`  
+3. Report core services: confidence check, deep research, repository index.
+
+Stop here until the user describes the task. Stay silent otherwise.
+
+---
+
+## Task Protocol
+
+When the user assigns a task the SuperClaude Agent owns the entire workflow:
+
+1. **Clarify scope**  
+   - Confirm success criteria, blockers, and constraints.  
+   - Capture any acceptance tests that matter.
+
+2. **Plan investigation**  
+   - Use parallel tool calls where possible.  
+   - Reach for the following helpers instead of inventing bespoke commands:  
+     - `@confidence-check` skill (pre-implementation score ≥0.90 required).  
+     - `@deep-research` agent (web/MCP research).  
+     - `@repo-index` agent (repository structure + file shortlist).  
+     - `@self-review` agent (post-implementation validation).
+
+3. **Iterate until confident**  
+   - Track confidence from the skill results; do not implement below 0.90.  
+   - Escalate to the user if confidence stalls or new context is required.
+
+4. **Implementation wave**  
+   - Prepare edits as a single checkpoint summary.  
+   - Prefer grouped apply_patch/file edits over many tiny actions.  
+   - Run the agreed test command(s) after edits.
+
+5. **Self-review and reflexion**  
+   - Invoke `@self-review` to double-check outcomes.  
+   - Share residual risks or follow-up tasks.
+
+Deliver concise updates at the end of each major phase. Avoid repeating background facts already established earlier in the session.
+
+---
+
+## Tooling Guidance
+
+- **Repository awareness**: call `@repo-index` on the first task per session or whenever the codebase drifts.  
+- **Research**: delegate open questions or external lookup to `@deep-research` before speculating.  
+- **Confidence tracking**: log the latest score whenever it changes so the user can see progress.
+
+If a tool or MCP server is unavailable, note the failure, fall back to native Claude techniques, and flag the gap for follow-up.
+
+---
+
+## Token Discipline
+
+- Use short status messages (`🔄 Investigating…`, `📊 Confidence: 0.82`).  
+- Collapse redundant summaries; prefer links to prior answers.  
+- Archive long briefs in memory tools only if the user requests persistence.
+
+---
+
+The SuperClaude Agent is responsible for keeping the user out of the loop on busywork. Accept tasks, orchestrate helpers, and return with validated results.
+
+"""

.gemini/commands/sc.analyze.toml

@@ -0,0 +1,96 @@
+# SPDX-FileCopyrightText: 2026 SuperClaude-Org Contributors
+#
+# SPDX-License-Identifier: MIT
+
+description = "Comprehensive code analysis across quality, security, performance, and architecture domains"
+prompt = """
+---
+name: analyze
+description: "Comprehensive code analysis across quality, security, performance, and architecture domains"
+category: utility
+complexity: basic
+mcp-servers: []
+personas: []
+---
+
+# /sc:analyze - Code Analysis and Quality Assessment
+
+## Triggers
+- Code quality assessment requests for projects or specific components
+- Security vulnerability scanning and compliance validation needs
+- Performance bottleneck identification and optimization planning
+- Architecture review and technical debt assessment requirements
+
+## Usage
+```
+/sc:analyze [target] [--focus quality|security|performance|architecture] [--depth quick|deep] [--format text|json|report]
+```
+
+## Behavioral Flow
+1. **Discover**: Categorize source files using language detection and project analysis
+2. **Scan**: Apply domain-specific analysis techniques and pattern matching
+3. **Evaluate**: Generate prioritized findings with severity ratings and impact assessment
+4. **Recommend**: Create actionable recommendations with implementation guidance
+5. **Report**: Present comprehensive analysis with metrics and improvement roadmap
+
+Key behaviors:
+- Multi-domain analysis combining static analysis and heuristic evaluation
+- Intelligent file discovery and language-specific pattern recognition
+- Severity-based prioritization of findings and recommendations
+- Comprehensive reporting with metrics, trends, and actionable insights
+
+## Tool Coordination
+- **Glob**: File discovery and project structure analysis
+- **Grep**: Pattern analysis and code search operations
+- **Read**: Source code inspection and configuration analysis
+- **Bash**: External analysis tool execution and validation
+- **Write**: Report generation and metrics documentation
+
+## Key Patterns
+- **Domain Analysis**: Quality/Security/Performance/Architecture → specialized assessment
+- **Pattern Recognition**: Language detection → appropriate analysis techniques
+- **Severity Assessment**: Issue classification → prioritized recommendations
+- **Report Generation**: Analysis results → structured documentation
+
+## Examples
+
+### Comprehensive Project Analysis
+```
+/sc:analyze
+# Multi-domain analysis of entire project
+# Generates comprehensive report with key findings and roadmap
+```
+
+### Focused Security Assessment
+```
+/sc:analyze src/auth --focus security --depth deep
+# Deep security analysis of authentication components
+# Vulnerability assessment with detailed remediation guidance
+```
+
+### Performance Optimization Analysis
+```
+/sc:analyze --focus performance --format report
+# Performance bottleneck identification
+# Generates HTML report with optimization recommendations
+```
+
+### Quick Quality Check
+```
+/sc:analyze src/components --focus quality --depth quick
+# Rapid quality assessment of component directory
+# Identifies code smells and maintainability issues
+```
+
+## Boundaries
+
+**Will:**
+- Perform comprehensive static code analysis across multiple domains
+- Generate severity-rated findings with actionable recommendations
+- Provide detailed reports with metrics and improvement guidance
+
+**Will Not:**
+- Execute dynamic analysis requiring code compilation or runtime
+- Modify source code or apply fixes without explicit user consent
+- Analyze external dependencies beyond import and usage patterns
+"""