What is the primary purpose of sparks-apply?

It ensures that Claude loads relevant project context and architectural patterns from a knowledge registry before starting any implementation or debugging task.

Why use this instead of just searching the codebase?

While searching finds code, this skill provides the 'why' behind the code, including past decisions, architectural patterns, and known pitfalls that standard searches often miss.

How does it find relevant knowledge?

It scans a central registry file located at .claude/skills/sparks-find/references/registry.toon for trigger words that match the user's current request.

Is it part of a larger framework?

Yes, it is an experimental feature within the SPECTRE workflow framework designed to enhance AI-driven development cycles.

Does it help with keeping documentation updated?

Yes, it requires Claude to proactively check if loaded skills need updating or if new knowledge should be captured after completing significant work.

Sparks Apply Knowledge

Name: Sparks Apply Knowledge
Author: Codename-Inc

byCodename-Inc

Productivity & Workflow

Automates the retrieval and maintenance of project-specific context and architectural patterns to ensure coding consistency.

About

Sparks-apply is a specialized workflow skill for Claude Code that mandates the loading of captured project knowledge before any task implementation or debugging begins. By checking a centralized knowledge registry based on task triggers, it prevents Claude from repeating past mistakes and ensures the AI adheres to established team decisions, patterns, and architectural context. Beyond simple retrieval, it enforces a proactive maintenance cycle where the AI updates documentation and 'sparks' modules as the codebase evolves, ensuring that the project's living documentation stays accurate and useful across sessions.

Key Features

Consistency enforcement for architectural decisions and team patterns
Proactive knowledge maintenance and automatic documentation updates
Mandatory trigger-based knowledge retrieval via a central registry
Integration with the SPECTRE workflow framework for high-context coding
0 GitHub stars
Prevention of redundant codebase searches and 'rediscovery' phases

Use Cases

Debugging recurring issues or 'gotchas' previously documented by the team
Starting a new feature implementation with existing architectural constraints
Maintaining a live project registry that evolves alongside the source code

About

Key Features

Consistency enforcement for architectural decisions and team patterns
Proactive knowledge maintenance and automatic documentation updates
Mandatory trigger-based knowledge retrieval via a central registry
Integration with the SPECTRE workflow framework for high-context coding
0 GitHub stars
Prevention of redundant codebase searches and 'rediscovery' phases

Use Cases

Debugging recurring issues or 'gotchas' previously documented by the team
Starting a new feature implementation with existing architectural constraints
Maintaining a live project registry that evolves alongside the source code