@xonovex/skills 0.1.9 → 0.1.15

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "xonovex",
   "description": "Xonovex coding guidelines and workflow skills for Claude Code",
-  "version": "0.1.0",
+  "version": "0.1.15",
   "author": {
     "name": "Xonovex"
   },

package/README.md

@@ -5,38 +5,147 @@ Xonovex coding guidelines and workflow skills for Claude Code.
 ## Installation
 
 ```bash
-claude mcp add @xonovex/skills
+# Install as npm package
+npm install @xonovex/skills
+
+# Or add the Xonovex marketplace (from within Claude Code)
+/plugin marketplace add xonovex/platform
+
+# Install the skills plugin
+/plugin install xonovex@xonovex-platform
+```
+
+Or test locally during development:
+
+```bash
+claude --plugin-dir ./packages/plugins/skills
 ```
 
-Or add to your Claude Code configuration manually.
+Skills are namespaced as `/xonovex:<skill-name>` (e.g., `/xonovex:typescript-guidelines`).
+
+## Coding Guidelines
+
+Auto-triggered guidelines that activate based on file type and context.
+
+### Languages
+
+| Skill                             | Description                                                                  |
+| --------------------------------- | ---------------------------------------------------------------------------- |
+| `typescript-guidelines`           | TypeScript Node.js ESM with strict mode, async/await, and Zod validation     |
+| `python-guidelines`               | Python 3.12+ with async/await, dataclasses, type hints, and pytest           |
+| `c99-guidelines`                  | Modern C99 with memory management, type safety, and error handling           |
+| `c99-opinionated-guidelines`      | Opinionated C99 for systems/game/embedded with data-oriented design and SIMD |
+| `c99-game-opinionated-guidelines` | Game engine patterns: caller-owns-memory, inverse mass, SoA optimization     |
+| `lua-guidelines`                  | Lua 5.4+ with module patterns, tables, coroutines, and error handling        |
+| `lua-opinionated-guidelines`      | LuaJIT performance patterns with JIT-friendly tables and pre-allocation      |
+| `typescript-to-lua-guidelines`    | TypeScript-to-Lua transpilation with TSTL 1.24+                              |
+| `shell-scripting-guidelines`      | POSIX shell scripts with strict mode, quoting, and idempotency               |
+| `sql-postgresql-guidelines`       | PostgreSQL 15+ with CTEs, indexing, JSONB, and row-level security            |
 
-## Features
+### Frameworks
 
-This plugin provides coding guidelines and workflow automation for:
+| Skill                         | Description                                                                |
+| ----------------------------- | -------------------------------------------------------------------------- |
+| `react-guidelines`            | React 19+ with Server Components, Form Actions, and React Compiler         |
+| `astro-guidelines`            | Astro static sites with islands architecture and content collections       |
+| `hono-guidelines`             | Hono 4.0+ API servers with validation, middleware, and WebSocket           |
+| `hono-opinionated-guidelines` | Opinionated Hono with inline OpenAPI handlers and router selection         |
+| `express.js-guidelines`       | Express 5+ API servers with route organization and Zod validation          |
+| `motion-react-guidelines`     | React animations with Motion: gestures, scroll effects, layout transitions |
+| `remotion-guidelines`         | Programmatic video with React using frame-driven animations                |
+| `threejs-guidelines`          | Vanilla Three.js with scene setup, materials, shaders, and post-processing |
 
-- **Languages**: TypeScript, Python, Lua, C99, Shell scripting
-- **Frameworks**: React, Express.js, Hono, Astro, Three.js, Remotion
-- **Infrastructure**: Docker, Kubernetes, Terraform, CMake
-- **Tools**: Git, Vitest, Zod, Motion
+### Infrastructure & Build
 
-## Available Skills
+| Skill                   | Description                                                               |
+| ----------------------- | ------------------------------------------------------------------------- |
+| `docker-guidelines`     | Docker multi-stage builds, security hardening, and optimization           |
+| `kubernetes-guidelines` | Kubernetes manifests with GitOps, Kustomize, and multi-environment config |
+| `terraform-guidelines`  | Terraform 1.12+ with module design and environment isolation              |
+| `cmake-guidelines`      | CMake 3.20+ target-based builds and dependency management                 |
+| `moon-guidelines`       | Moonrepo monorepo task management with inheritance and project tagging    |
 
-### Coding Guidelines
+### Testing & Validation
 
-- `typescript-guidelines` - TypeScript best practices
-- `react-guidelines` - React 19+ patterns
-- `python-guidelines` - Python 3.12+ conventions
-- `docker-guidelines` - Docker/containerization
-- `kubernetes-guidelines` - Kubernetes manifests
-- `terraform-guidelines` - Infrastructure as code
-- `git-guidelines` - Git workflow and commits
+| Skill               | Description                                                            |
+| ------------------- | ---------------------------------------------------------------------- |
+| `vitest-guidelines` | Vitest 3+ with type safety, HTTP testing, and mock patterns            |
+| `zod-guidelines`    | Zod 4.0+ runtime validation with schema composition and type inference |
+
+### Paradigms
+
+| Skill                    | Description                                                               |
+| ------------------------ | ------------------------------------------------------------------------- |
+| `general-fp-guidelines`  | Functional programming with pure functions, immutability, and composition |
+| `general-oop-guidelines` | Object-oriented programming with SOLID principles and design patterns     |
+
+### Meta & Content
+
+| Skill                     | Description                                                                  |
+| ------------------------- | ---------------------------------------------------------------------------- |
+| `git-guidelines`          | Git conventional commits, merge conflict resolution, and worktree management |
+| `skill-guidelines`        | Creating and managing guideline skills with progressive disclosure           |
+| `plan-guidelines`         | Planning research and analysis tasks with code alignment and simplification  |
+| `insights-guidelines`     | Extracting insights from development sessions and integrating into skills    |
+| `instruction-guidelines`  | Working with AGENTS.md/CLAUDE.md project instruction files                   |
+| `content-guidelines`      | Bilingual content creation with structured formatting and CEFR levels        |
+| `presentation-guidelines` | Creating presentations from codebase analysis with diagrams and Motion       |
+| `strudel-guidelines`      | Algorithmic music generation with Strudel.cc and mini-notation               |
+
+## Workflow
+
+Plan-driven development workflow with worktree isolation and parallel execution.
+
+```
++---------------------+     +---------------------+     +---------------------+
+|      Research       |     |      Planning       |     |   Worktree Setup    |
++---------------------+     +---------------------+     +---------------------+
+| /plan-research      |---->| /plan-create        |---->| /plan-worktree-     |
+|   - viability       |     | /plan-subplans-     |     |       create        |
+|   - alternatives    |     |       create        |     |                     |
++---------------------+     | /plan-tdd-create    |     +---------------------+
+                            +---------------------+               |
+            +------------------------------------------------------+
+            |
+            v
++---------------------+     +---------------------+     +---------------------+
+|  Development Loop   |     |    Code Quality     |     |        Merge        |
++---------------------+     +---------------------+     +---------------------+
+| /plan-continue      |---->| /code-simplify      |---->| /plan-worktree-     |
+| (implement)         |     | /code-harden        |     |       merge         |
+| /plan-validate      |     | /code-align         |     | /git-commit --push  |
+| /insights-extract   |     |                     |     +---------------------+
+| /plan-update        |     +---------------------+               |
++---------------------+            |                              |
+            ^                      |                              v
+            |                      |                    +---------------------+
+            +--- more subplans? ---+                    |        Done         |
+                                                        +---------------------+
+
+Parallel: Multiple agents work on parallel subplan groups in separate worktrees
+Learning: /insights-integrate merges learnings into guidelines for future sessions
+```
 
 ### Workflow Commands
 
-- `/commit` - Create conventional commits
-- `/plan-create` - Create implementation plans
-- `/plan-continue` - Resume work from a plan
-- `/insights-extract` - Extract lessons learned
+| Command                  | Description                                                    |
+| ------------------------ | -------------------------------------------------------------- |
+| `/plan-research`         | Research codebase and web for viability and alternatives       |
+| `/plan-create`           | Create a high-level plan with research for user review         |
+| `/plan-tdd-create`       | Create a TDD plan with atomic test step proposals              |
+| `/plan-subplans-create`  | Generate detailed subplans with parallel execution detection   |
+| `/plan-continue`         | Resume work from an existing plan document                     |
+| `/plan-validate`         | Verify that plan objectives have been fully achieved           |
+| `/plan-update`           | Update plan status, phase, and timestamps                      |
+| `/plan-worktree-create`  | Create a git worktree for isolated feature development         |
+| `/plan-worktree-merge`   | Merge feature worktree back to source with conflict resolution |
+| `/plan-worktree-abandon` | Document and abandon a feature with reason and learnings       |
+| `/code-simplify`         | Analyze code for consolidation and dead code removal           |
+| `/code-harden`           | Analyze code for type safety, validation, and error handling   |
+| `/code-align`            | Compare two implementations for structural differences         |
+| `/git-commit`            | Auto-generate conventional commit messages with optional push  |
+| `/insights-extract`      | Extract development mistakes and lessons from the session      |
+| `/insights-integrate`    | Convert extracted insights into guideline skills               |
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xonovex/skills",
-  "version": "0.1.9",
+  "version": "0.1.15",
   "description": "Xonovex coding guidelines and workflow skills for Claude Code",
   "license": "MIT",
   "author": "Xonovex",

package/skills/astro-guidelines/reference/accessibility.md

@@ -24,6 +24,7 @@
 ```
 
 **Techniques:**
+
 - Semantic elements: Use `<header>`, `<nav>`, `<main>`, `<article>`, `<aside>` for structure
 - Alt text: Provide descriptive alt attributes for all images
 - Heading hierarchy: Maintain h1 → h2 → h3 logical ordering

package/skills/astro-guidelines/reference/components.md

@@ -16,8 +16,9 @@ interface Props {
   variant?: "default" | "featured";
 }
 
-const { title, description, href, variant = "default" } = Astro.props;
+const {title, description, href, variant = "default"} = Astro.props;
 ---
+
 <div class={`card card--${variant}`}>
   <h3>{title}</h3>
   {description && <p>{description}</p>}
@@ -29,12 +30,20 @@ const { title, description, href, variant = "default" } = Astro.props;
   </div>
 </div>
 <style>
-  .card { border: 1px solid #ddd; padding: 1rem; border-radius: 8px; }
-  .card--featured { border-color: #0066cc; background: #f0f8ff; }
+  .card {
+    border: 1px solid #ddd;
+    padding: 1rem;
+    border-radius: 8px;
+  }
+  .card--featured {
+    border-color: #0066cc;
+    background: #f0f8ff;
+  }
 </style>
 ```
 
 **Techniques:**
+
 - Astro components: Create `.astro` components for static presentational UI
 - Props typing: Use TypeScript interfaces for type-safe component props
 - Slots composition: Leverage slots for flexible component composition

package/skills/astro-guidelines/reference/content-collections.md

@@ -25,6 +25,7 @@ export const collections = {
 ```
 
 **Techniques:**
+
 - Collection schemas: Define Zod schemas in `src/content/config.ts` for validation
 - Directory structure: Organize content in `src/content/[collection-name]/` directories
 - Query functions: Use `getCollection()` and `getEntry()` for type-safe queries

package/skills/astro-guidelines/reference/islands-architecture.md

@@ -11,14 +11,18 @@
 import Counter from "../components/Counter.tsx";
 import SearchBar from "../components/SearchBar.tsx";
 ---
+
 <Layout title="Home">
   <h1>Static Content</h1>
-  <Counter client:visible />        <!-- Hydrate on viewport entry -->
-  <SearchBar client:load />         <!-- Hydrate immediately -->
+  <Counter client:visible />
+  <!-- Hydrate on viewport entry -->
+  <SearchBar client:load />
+  <!-- Hydrate immediately -->
 </Layout>
 ```
 
 **Techniques:**
+
 - Static by default: Build pages with Astro components that render zero JavaScript
 - Framework components: Import React, Vue, Svelte only for interactive features
 - client:load: Hydrate immediately for critical interactive components

package/skills/astro-guidelines/reference/project-structure.md

@@ -25,6 +25,7 @@ src/
 ```
 
 **Techniques:**
+
 - Pages directory: Place routes in `src/pages/` for automatic file-based routing
 - Components folder: Store reusable components in `src/components/`
 - Layouts directory: Create reusable layouts in `src/layouts/`

package/skills/c99-game-opinionated-guidelines/reference/builder-pattern.md

@@ -22,6 +22,7 @@ status_t status = sphere_mesh3d_build(&mesh, 1.0f, 32, 16);
 ```
 
 **Techniques:**
+
 - Query phase: Call `*_req()` to get exact vertex/index counts needed
 - Caller allocation: Choose strategy (stack, malloc, arena) for complete control
 - Build phase: Call `*_build()` to fill pre-allocated caller buffer

package/skills/c99-game-opinionated-guidelines/reference/coordinate-system.md

@@ -20,6 +20,7 @@ matrix4f_t view_lh = matrix4f_look_at_lh(eye, target, up);
 ```
 
 **Techniques:**
+
 - Right-handed default: Use +X right, +Y up, +Z forward as base convention
 - CCW winding: Define front faces with counter-clockwise vertex order
 - Suffix variants: Provide `_rh` and `_lh` function suffixes for explicit systems

package/skills/c99-game-opinionated-guidelines/reference/geometry-pipeline.md

@@ -22,6 +22,7 @@ mesh3d_pack_3f_4u8(packed, &mesh, color);
 ```
 
 **Techniques:**
+
 - Analytic layer: Define shapes like `sphere3d_t`, `circle2d_t` for physics/logic
 - Discrete layer: Build indexed meshes from analytic shapes with builder pattern
 - Packing layer: Convert mesh to GPU-ready vertex formats (interleaved/streaming)

package/skills/c99-game-opinionated-guidelines/reference/math-types.md

@@ -24,7 +24,8 @@ m.columns[3] = (vec4f_t){.x = tx, .y = ty, .z = tz, .w = 1.0f};
 ```
 
 **Techniques:**
-- 16-byte alignment: Pad vec3 with _pad field for SIMD-friendly 16B size
+
+- 16-byte alignment: Pad vec3 with \_pad field for SIMD-friendly 16B size
 - Union design: Combine named fields with array access for flexibility
 - Column-major matrices: Store matrix4f_t as 4 column vectors
 - Quaternion format: Use x, y, z, w order with normalization constraint

package/skills/c99-game-opinionated-guidelines/reference/mesh-types.md

@@ -25,6 +25,7 @@ typedef struct {
 ```
 
 **Techniques:**
+
 - Capacity tracking: Maintain separate count and capacity for dynamic growth
 - Builder pattern: Use `{shape}_mesh{dim}_{req|build}` naming convention
 - Optional data: Include normals/UVs in mesh3d for advanced rendering

package/skills/c99-game-opinionated-guidelines/reference/physics-patterns.md

@@ -21,6 +21,7 @@ void apply_impulse(rigidbody_t *rb, vec3f_t impulse) {
 ```
 
 **Techniques:**
+
 - Inverse mass: Store `inv_mass` (1/mass); zero for static bodies to disable movement
 - Bit flags: Use `uint32_t` with bitmask enums for state like ACTIVE, SLEEPING
 - Sync maps: Index maps decouple physics arrays from entity system arrays

package/skills/c99-game-opinionated-guidelines/reference/spatial-structures.md

@@ -2,7 +2,7 @@
 
 **Guideline:** Use dimension-suffixed structures (grid, tree, bvh) for broad-phase queries. Choose by density/pattern.
 
-**Rationale:** Different structures suit different spatial distributions; dimension suffixes (_2d, _3d) enable consistent APIs across dimensions.
+**Rationale:** Different structures suit different spatial distributions; dimension suffixes (\_2d, \_3d) enable consistent APIs across dimensions.
 
 **Example:**
 
@@ -19,6 +19,7 @@ uint32_t cell_idx = cell_y * g->cells_x + cell_x;
 ```
 
 **Techniques:**
+
 - Uniform grids: Use for dense/uniform object distributions with O(1) insertion
 - Quadtrees/Octrees: Use for sparse/varying density with O(log n) operations
 - BVH structures: Use for static geometry and ray casting queries

package/skills/c99-game-opinionated-guidelines/reference/tagged-unions.md

@@ -33,6 +33,7 @@ float shape_volume(const shape_t *s) {
 ```
 
 **Techniques:**
+
 - Type enum: Define all variant types in single enum for exhaustiveness
 - Union members: Create named structs within union for each type variant
 - Switch dispatch: Use switch on type field with no default clause

package/skills/c99-game-opinionated-guidelines/reference/vertex-packing.md

@@ -31,6 +31,7 @@ size_t mesh3d_pack_size(const mesh3d_t *m, vertex_format_t fmt) {
 ```
 
 **Techniques:**
+
 - Vertex format naming: Use `vertex_{components}_{types}_t` (e.g., `vertex_3f_4u8_t`)
 - Interleaved layout: Pack all attributes per-vertex in single buffer
 - Streaming layout: Separate position/normal/UV into different buffers

package/skills/c99-guidelines/reference/compound-literals.md

@@ -26,6 +26,7 @@ void example(void) {
 ```
 
 **Techniques:**
+
 - Inline syntax: Use `(Type){initializer-list}` to create temporaries inline
 - With designators: Combine with designated initializers for clarity
 - Function arguments: Create temporary structs directly in function calls

package/skills/c99-guidelines/reference/const-correctness.md

@@ -25,6 +25,7 @@ const char *get_name(void) {
 ```
 
 **Techniques:**
+
 - Read-only parameters: Mark function parameters with const when not modified
 - Pointer variants: Distinguish `const T *p` (pointer to const) vs `T *const p` (const pointer)
 - Return values: Use const for immutable return values to prevent modification

package/skills/c99-guidelines/reference/designated-initializers.md

@@ -25,6 +25,7 @@ int days[12] = {
 ```
 
 **Techniques:**
+
 - Field syntax: Use `.field = value` for struct initialization with clarity
 - Array syntax: Use `[index] = value` for sparse array initialization
 - Partial init: Unspecified fields are automatically zeroed without explicit values

package/skills/c99-guidelines/reference/error-handling.md

@@ -42,6 +42,7 @@ error_t load_file(const char *path, char **out, size_t *len) {
 ```
 
 **Techniques:**
+
 - Error enums: Define descriptive error types with zero for success
 - Output parameters: Use pointers to return multiple results alongside error codes
 - Error checking: Always check return values immediately after function calls

package/skills/c99-guidelines/reference/inline-functions.md

@@ -30,6 +30,7 @@ int result = clampi(x++, 0, 10);
 ```
 
 **Techniques:**
+
 - Replace macros: Replace function-like macros with `static inline` functions
 - Type-specific variants: Create `clampi`, `clampf` instead of generic macro
 - Header placement: Use inline functions in headers for no multiple definition issues

package/skills/c99-guidelines/reference/memory-management.md

@@ -28,6 +28,7 @@ void dynamic_array(size_t size) {
 ```
 
 **Techniques:**
+
 - Default stack: Use stack allocation for fixed-size data by default
 - Heap when needed: Use malloc/calloc only for dynamic or longer-lived data
 - Malloc/free pairing: Always pair every malloc with corresponding free call

package/skills/c99-opinionated-guidelines/reference/alignment.md

@@ -43,6 +43,7 @@ void *aligned_alloc_16(size_t size) {
 ```
 
 **Techniques:**
+
 - SIMD alignment: Pad vec3 to 16-byte aligned structures for SIMD instructions
 - Compiler directives: Use `_Alignas(16)` for explicit struct field alignment
 - SoA layout: Align array-of-structures for batch SIMD operations

package/skills/c99-opinionated-guidelines/reference/caller-owns-memory.md

@@ -31,6 +31,7 @@ status_t entity_add(entity_system_t *sys, float x, float y) {
 ```
 
 **Techniques:**
+
 - Functions receive pointers: Accept caller-provided storage instead of allocating
 - Init functions: Bind library state to caller-owned arrays with capacity tracking
 - Status returns: Return status codes, never allocated pointers

package/skills/c99-opinionated-guidelines/reference/compound-literals.md

@@ -26,6 +26,7 @@ void example(void) {
 ```
 
 **Techniques:**
+
 - Inline syntax: Use `(Type){initializer-list}` to create temporaries inline
 - With designators: Combine with designated initializers for clarity
 - Function arguments: Create temporary structs directly in function calls

package/skills/c99-opinionated-guidelines/reference/const-correctness.md

@@ -25,6 +25,7 @@ const char *get_name(void) {
 ```
 
 **Techniques:**
+
 - Read-only parameters: Mark function parameters with const when not modified
 - Pointer variants: Distinguish `const T *p` (pointer to const) vs `T *const p` (const pointer)
 - Return values: Use const for immutable return values to prevent modification

package/skills/c99-opinionated-guidelines/reference/data-oriented-design.md

@@ -35,6 +35,7 @@ for (size_t i = 0; i < system.count; i++) {
 ```
 
 **Techniques:**
+
 - Separate fields: Move frequently accessed fields into their own arrays
 - Cache locality: Sequential memory access maximizes CPU cache utilization
 - Array sync: Keep indices synchronized across all component arrays

package/skills/c99-opinionated-guidelines/reference/designated-initializers.md

@@ -25,6 +25,7 @@ int days[12] = {
 ```
 
 **Techniques:**
+
 - Field syntax: Use `.field = value` for struct initialization with clarity
 - Array syntax: Use `[index] = value` for sparse array initialization
 - Partial init: Unspecified fields are automatically zeroed without explicit values

package/skills/c99-opinionated-guidelines/reference/error-handling.md

@@ -42,6 +42,7 @@ error_t load_file(const char *path, char **out, size_t *len) {
 ```
 
 **Techniques:**
+
 - Error enums: Define descriptive error types with zero for success
 - Output parameters: Use pointers to return multiple results alongside error codes
 - Error checking: Always check return values immediately after function calls

package/skills/c99-opinionated-guidelines/reference/file-naming.md

@@ -26,6 +26,7 @@ vector.test.c        # Scalar tests
 ```
 
 **Techniques:**
+
 - Type suffix: Use `_type.h` for type definitions only
 - Impl suffix: Use `_impl.h` for inline scalar implementations
 - Batch variants: Use `_aos.h`, `_soa.h` for batch implementations

package/skills/c99-opinionated-guidelines/reference/implementation-variants.md

@@ -28,6 +28,7 @@ void vec3_dot_soa(float *out, const vec3_soa_t *a, const vec3_soa_t *b) {
 ```
 
 **Techniques:**
+
 - Scalar single: Start with single-object reference implementation for debugging
 - AoS batch: Add batch processing for struct arrays (1.5x speedup)
 - SoA batch: Add cache-friendly variant for large workloads (2-3x speedup)

package/skills/c99-opinionated-guidelines/reference/inline-functions.md

@@ -30,6 +30,7 @@ int result = clampi(x++, 0, 10);
 ```
 
 **Techniques:**
+
 - Replace macros: Replace function-like macros with `static inline` functions
 - Type-specific variants: Create `clampi`, `clampf` instead of generic macro
 - Header placement: Use inline functions in headers for no multiple definition issues

package/skills/c99-opinionated-guidelines/reference/memory-management.md

@@ -28,6 +28,7 @@ void dynamic_array(size_t size) {
 ```
 
 **Techniques:**
+
 - Default stack: Use stack allocation for fixed-size data by default
 - Heap when needed: Use malloc/calloc only for dynamic or longer-lived data
 - Malloc/free pairing: Always pair every malloc with corresponding free call

package/skills/c99-opinionated-guidelines/reference/safety-validations.md

@@ -25,6 +25,7 @@ vec3_t vec3_normalize(const vec3_t *v) {
 ```
 
 **Techniques:**
+
 - Capacity checks: Validate `used + size <= capacity` before writing
 - Bounds checks: Check `idx < count` before array access
 - NULL checks: Test `if (!ptr)` at function entry

package/skills/c99-opinionated-guidelines/reference/testing-patterns.md

@@ -32,6 +32,7 @@ void test_vec3_dot_soa_parity(void) {
 ```
 
 **Techniques:**
+
 - Typed assertions: Use `assert_int_eq`, `assert_float_eq`, `assert_ptr_not_null`
 - Epsilon values: Use 1e-4f general, 1e-5f cumulative, 5e-4f for SIMD
 - Scalar tests: Validate against known values for correctness

package/skills/cmake-guidelines/reference/compile-options.md

@@ -1,6 +1,6 @@
 # compile-options: Compile Options and Definitions
 
-**Guideline:** Set compiler flags, definitions, and features on targets using target_compile_* commands with appropriate visibility.
+**Guideline:** Set compiler flags, definitions, and features on targets using target*compile*\* commands with appropriate visibility.
 
 **Rationale:** Target-scoped settings prevent pollution of the global build environment and allow different targets to have different requirements.
 
@@ -27,6 +27,7 @@ target_compile_features(mylib PUBLIC cxx_std_20)
 ```
 
 **Techniques:**
+
 - target_compile_options(): Set compiler-specific flags with generator expressions
 - target_compile_definitions(): Define preprocessor macros with visibility control
 - target_compile_features(): Require C++ standard using cxx_std_20, cxx_std_17, etc

package/skills/cmake-guidelines/reference/fetchcontent.md

@@ -25,6 +25,7 @@ target_link_libraries(app PRIVATE fmt::fmt)
 ```
 
 **Techniques:**
+
 - FetchContent_Declare(): Declare dependency with git repo and version pin
 - GIT_TAG: Pin exact version for reproducible builds
 - GIT_SHALLOW: Use shallow clone for faster fetching

package/skills/cmake-guidelines/reference/find-package.md

@@ -22,8 +22,9 @@ endif()
 ```
 
 **Techniques:**
+
 - REQUIRED: Fail build if package not found, use for mandatory dependencies
 - COMPONENTS: Specify individual package parts to reduce linking
 - Namespaced targets: Use Boost::system, OpenSSL::SSL for safe target linking
-- \*_FOUND variable: Check if optional dependency is available before using
+- \*\_FOUND variable: Check if optional dependency is available before using
 - Conditional linking: Add target_compile_definitions when dependencies found

package/skills/cmake-guidelines/reference/generator-expressions.md

@@ -27,6 +27,7 @@ target_compile_definitions(mylib PRIVATE
 ```
 
 **Techniques:**
+
 - BUILD_INTERFACE/INSTALL_INTERFACE: Different paths for build vs installed consumption
 - CXX_COMPILER_ID: Detect compiler and apply vendor-specific flags
 - CONFIG: Apply Debug or Release build-specific settings

package/skills/cmake-guidelines/reference/installation.md

@@ -31,6 +31,7 @@ install(EXPORT mylib-targets
 ```
 
 **Techniques:**
+
 - install(TARGETS): Install libraries and executables with type-specific destinations
 - EXPORT: Create importable CMake files for downstream find_package() calls
 - DESTINATION: Set lib/bin/include paths for each artifact type

package/skills/cmake-guidelines/reference/project-structure.md

@@ -33,6 +33,7 @@ add_test(NAME core_test COMMAND core_test)
 ```
 
 **Techniques:**
+
 - cmake_minimum_required(): Set 3.20+ for modern CMake features
 - project(): Declare name, version, description, and required languages
 - add_library/add_executable(): Create targets for libraries and binaries

package/skills/cmake-guidelines/reference/target-types.md

@@ -30,6 +30,7 @@ add_executable(gui WIN32 MACOSX_BUNDLE src/gui.cpp)
 ```
 
 **Techniques:**
+
 - add_library() without type: Let BUILD_SHARED_LIBS control static vs shared
 - STATIC: Always statically link, good for embedded or single-binary scenarios
 - SHARED: Dynamic library for runtime linking and flexible updates

package/skills/cmake-guidelines/reference/testing.md

@@ -23,6 +23,7 @@ set_tests_properties(unit_tests PROPERTIES TIMEOUT 30 LABELS "unit")
 ```
 
 **Techniques:**
+
 - enable_testing(): Enable the testing feature in CMake project
 - add_test(): Register test executable or command with optional working directory
 - set_tests_properties(): Set timeout, labels, or other test attributes

package/skills/cmake-guidelines/reference/visibility-specifiers.md

@@ -25,6 +25,7 @@ target_link_libraries(app PRIVATE mylib PUBLIC common INTERFACE interface)
 ```
 
 **Techniques:**
+
 - PUBLIC: Properties visible to both target and all downstream consumers
 - PRIVATE: Properties used only by target, not propagated to consumers
 - INTERFACE: Properties for consumers only, not used by target itself