@booklib/core 2.0.0

package/booklib-router.mdc

@@ -0,0 +1,36 @@
+---
+description: "BookLib Knowledge Router. Consult this to find the right architectural rules for any task."
+globs: "*"
+---
+
+# 📚 BookLib Knowledge Router
+
+You have access to a sophisticated, local semantic search engine that indexes a library of distilled software architecture books.
+
+**CRITICAL RULE:** Do not rely on your generic training data for complex architectural decisions. You MUST query the BookLib index.
+
+## When to Search:
+- Designing a new system or module.
+- Refactoring legacy code.
+- Reviewing code for quality or idiomatic patterns.
+- Choosing between different architectural patterns (e.g., Saga vs. Two-Phase Commit).
+
+## How to Search:
+Use the following terminal command to retrieve relevant principles and anti-patterns:
+`node bin/booklib.js search "<your conceptual query>"`
+
+## Integrated Skills:
+- **Clean Code**: naming, functions, classes, error handling.
+- **DDD**: bounded contexts, aggregates, entities, value objects.
+- **Effective Kotlin/Java/Python/TypeScript**: language-specific idiomatic patterns.
+- **Data Intensive Patterns**: replication, partitioning, consistency models.
+- **System Design**: scalability, estimation, high-level architecture.
+
+<execution_rule>
+After performing a search, apply the retrieved principles and you MUST cite the source book or item in your final output.
+</execution_rule>
+
+<handoff_rule>
+If you see a `.booklib/handoff.md` file, you MUST read it immediately to understand the context from the previous agent session. 
+Before finishing a session, ask the user if they want to `save-state` for the next agent.
+</handoff_rule>

package/booklib.config.json

@@ -0,0 +1,19 @@
+{
+  "sources": [
+    { "type": "registry", "trusted": true },
+    { "type": "manifest", "url": "./community/registry.json", "trusted": true },
+    { "type": "github-skills-dir", "repo": "affaan-m/everything-claude-code", "dir": "skills", "branch": "main", "trusted": true, "artifacts": ["rules", "agents", "commands"] },
+    { "type": "github-skills-dir", "repo": "ehmo/platform-design-skills", "dir": "skills", "branch": "main", "trusted": true },
+    { "type": "github-skills-dir", "repo": "anthropics/skills", "dir": "skills", "branch": "main", "trusted": true },
+    { "type": "github-skills-dir", "repo": "emilkowalski/skill", "dir": "skills", "branch": "main", "trusted": true },
+    { "type": "github-skills-dir", "repo": "obra/superpowers", "dir": "skills", "branch": "main", "trusted": true },
+    { "type": "github-skills-dir", "repo": "ruvnet/ruflo", "dir": ".claude/skills", "branch": "main", "trusted": true }
+  ],
+  "discovery": {
+    "ttlHours": 24
+  },
+  "search": {
+    "minScore": 0.3,
+    "registryFallbackThreshold": 0.4
+  }
+}

package/commands/animation-at-work.md

@@ -0,0 +1,10 @@
+---
+description: Review web animations using Animation at Work principles (Rachel Nabors). Usage: /animation-at-work [file | component]
+---
+
+Apply the `animation-at-work` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review changed animation code.
+
+Focus on purpose, duration, easing, performance (compositor-only properties), and accessibility (prefers-reduced-motion). Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/clean-code-reviewer.md

@@ -0,0 +1,10 @@
+---
+description: Review code against Clean Code principles (Robert C. Martin). Usage: /clean-code-reviewer [file | path]
+---
+
+Apply the `clean-code-reviewer` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Classify each finding as **HIGH** (correctness, naming that obscures intent), **MEDIUM** (design, structure), or **LOW** (style). Reference every finding as `file:line`.

package/commands/data-intensive-patterns.md

@@ -0,0 +1,10 @@
+---
+description: Review data storage and distributed systems patterns (DDIA, Martin Kleppmann). Usage: /data-intensive-patterns [file | path]
+---
+
+Apply the `data-intensive-patterns` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on replication, partitioning, transactions, consistency models, and storage engine trade-offs. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/data-pipelines.md

@@ -0,0 +1,10 @@
+---
+description: Review data pipeline code using Data Pipelines Pocket Reference (James Densmore). Usage: /data-pipelines [file | path]
+---
+
+Apply the `data-pipelines` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on ingestion, transformation, orchestration, error handling, idempotency, and observability. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/design-patterns.md

@@ -0,0 +1,10 @@
+---
+description: Review OO design and apply GoF patterns (Head First Design Patterns). Usage: /design-patterns [file | path]
+---
+
+Apply the `design-patterns` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Identify which GoF patterns are present, misapplied, or missing. Flag over-engineering. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/domain-driven-design.md

@@ -0,0 +1,10 @@
+---
+description: Review domain models using DDD patterns (Eric Evans). Usage: /domain-driven-design [file | path]
+---
+
+Apply the `domain-driven-design` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on Aggregates, Entities, Value Objects, Bounded Contexts, and domain invariants. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/effective-java.md

@@ -0,0 +1,10 @@
+---
+description: Review Java code against Effective Java items (Joshua Bloch). Usage: /effective-java [file | path]
+---
+
+Apply the `effective-java` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on generics, builders, enums, exceptions, and API design. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/effective-kotlin.md

@@ -0,0 +1,10 @@
+---
+description: Review Kotlin code against Effective Kotlin best practices (Marcin Moskała). Usage: /effective-kotlin [file | path]
+---
+
+Apply the `effective-kotlin` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on safety, readability, idiomatic Kotlin, and common pitfalls. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/effective-python.md

@@ -0,0 +1,10 @@
+---
+description: Review Python code against Effective Python practices (Brett Slatkin). Usage: /effective-python [file | path]
+---
+
+Apply the `effective-python` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on Pythonic idioms, list/dict usage, comprehensions, classes, and robustness. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/effective-typescript.md

@@ -0,0 +1,10 @@
+---
+description: Review TypeScript code against Effective TypeScript (Dan Vanderkam). Usage: /effective-typescript [file | path]
+---
+
+Apply the `effective-typescript` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on type design, avoiding `any`, structural typing, and type inference. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/kotlin-in-action.md

@@ -0,0 +1,10 @@
+---
+description: Review Kotlin code using Kotlin in Action patterns (Elizarov, Isakova). Usage: /kotlin-in-action [file | path]
+---
+
+Apply the `kotlin-in-action` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on language features: coroutines, extension functions, sealed classes, delegation, and DSL patterns. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/lean-startup.md

@@ -0,0 +1,10 @@
+---
+description: Evaluate product/feature decisions using The Lean Startup framework (Eric Ries). Usage: /lean-startup [feature description | file]
+---
+
+Apply the `lean-startup` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, describe the feature or product decision you want evaluated.
+
+Focus on validated learning, Build-Measure-Learn cycle, MVP scope, pivot signals, and vanity vs. actionable metrics.

package/commands/microservices-patterns.md

@@ -0,0 +1,10 @@
+---
+description: Review microservice architecture using patterns from Chris Richardson. Usage: /microservices-patterns [file | path | description]
+---
+
+Apply the `microservices-patterns` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on service decomposition, sagas, event sourcing, API gateways, and inter-service communication. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/programming-with-rust.md

@@ -0,0 +1,10 @@
+---
+description: Review Rust code against Programming with Rust (Donis Marshall). Usage: /programming-with-rust [file | path]
+---
+
+Apply the `programming-with-rust` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on ownership, borrowing, lifetimes, traits, and safe concurrency patterns. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/refactoring-ui.md

@@ -0,0 +1,10 @@
+---
+description: Review UI design against Refactoring UI principles (Wathan & Schoger). Usage: /refactoring-ui [file | component | screenshot path]
+---
+
+Apply the `refactoring-ui` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review changed UI components.
+
+Focus on visual hierarchy, spacing, typography, color, and component composition. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/rust-in-action.md

@@ -0,0 +1,10 @@
+---
+description: Review Rust code using Rust in Action patterns (Tim McNamara). Usage: /rust-in-action [file | path]
+---
+
+Apply the `rust-in-action` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on systems programming idioms: memory layout, unsafe code, FFI, and OS interaction. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/skill-router.md

@@ -0,0 +1,10 @@
+---
+description: Route your task to the most relevant booklib skill. Usage: /skill-router [file | task description]
+---
+
+Apply the `skill-router` skill to recommend the best @booklib skill for this task.
+
+**Input:** $ARGUMENTS
+If no input was given, use `git diff HEAD` as the scope.
+
+Return a ranked recommendation with rationale and anti-triggers. Then ask if you should apply the recommended skill immediately.

package/commands/spring-boot-in-action.md

@@ -0,0 +1,10 @@
+---
+description: Review Spring Boot code using Spring Boot in Action patterns (Craig Walls). Usage: /spring-boot-in-action [file | path]
+---
+
+Apply the `spring-boot-in-action` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on auto-configuration, dependency injection, REST endpoints, data access, and testing. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/storytelling-with-data.md

@@ -0,0 +1,10 @@
+---
+description: Review data visualizations and charts using Storytelling with Data (Cole Nussbaumer Knaflic). Usage: /storytelling-with-data [file | chart description]
+---
+
+Apply the `storytelling-with-data` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, describe the chart or run `git diff HEAD` to review changed visualization code.
+
+Focus on chart type choice, data-ink ratio, clutter removal, audience, and narrative. Classify each finding as **HIGH** / **MEDIUM** / **LOW**.

package/commands/system-design-interview.md

@@ -0,0 +1,10 @@
+---
+description: Review system design using Alex Xu's framework (scalability, estimation, trade-offs). Usage: /system-design-interview [description | file]
+---
+
+Apply the `system-design-interview` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, describe the system you want reviewed or run `git diff HEAD`.
+
+Cover requirements clarification, capacity estimation, high-level design, component deep-dive, and trade-offs. Classify each finding as **HIGH** / **MEDIUM** / **LOW**.

package/commands/using-asyncio-python.md

@@ -0,0 +1,10 @@
+---
+description: Review Python async/concurrent code using Using Asyncio in Python (Caleb Hattingh). Usage: /using-asyncio-python [file | path]
+---
+
+Apply the `using-asyncio-python` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on event loop usage, coroutine patterns, task management, cancellation, and common asyncio pitfalls. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.

package/commands/web-scraping-python.md

@@ -0,0 +1,10 @@
+---
+description: Review Python web scraping code using Web Scraping with Python (Ryan Mitchell). Usage: /web-scraping-python [file | path]
+---
+
+Apply the `web-scraping-python` skill.
+
+**Target:** $ARGUMENTS
+If no target was given, run `git diff HEAD` and review those changes.
+
+Focus on selector robustness, rate limiting, error handling, anti-bot evasion, and data storage. Classify each finding as **HIGH** / **MEDIUM** / **LOW** and reference as `file:line`.