project-context-router

Included with Lifetime

$97 forever

Decide where instructions, memory, plans, and artifacts should live between global Codex baseline and project-specific files. Use when creating/updating AGENTS/ROADMAP/memory docs, introducing new workflow rules, or deciding whether content belongs in ~/.codex/rules versus a repository.

Writing & Docs

What this skill does

# Project Context Router

## Overview
Apply a deterministic routing workflow so each update is stored once, in the correct scope, with minimal duplication.

## Routing Workflow
1. Identify the content type.
2. Determine the scope (`global`, `project`, or `target-project`).
3. Write/update only the owning file.
4. Add a one-line cross-reference only if discoverability is required.
5. Reject duplicate copies in multiple scopes.

## Scope Decision Matrix
- Global (`~/.codex/rules`):
- Cross-project behavior, operating principles, tool policy, global roadmap.
- Examples: `AGENTS.md`, `principles.md`, `soul.md`, `default.rules`, global `ROADMAP.md`.
- Project (current repository):
- Repo-specific product goals, architecture, implementation roadmap, diagnostics, tests.
- Examples: repository `AGENTS.md`, repository `ROADMAP.md`, task-specific docs.
- Target project operated by Jarvis (cloned app repos):
- `JARVIS.md` and project execution memory for that target app.
- Do not place target-project operational memory into global rules.

## Content-Type Routing Rules
- Principles/identity:
- Global unless explicitly tied to one repository.
- Workflow policy:
- Global if reusable across projects; project if tied to one codebase/toolchain.
- Roadmaps:
- Keep one global roadmap in `~/.codex/rules/ROADMAP.md`.
- Keep one roadmap per repository in `<repo>/ROADMAP.md`.
- Memory:
- Global memory only for cross-project durable learnings.
- Project memory for repo-specific regressions and decisions.
- Agent instructions:
- Codex global instructions in `~/.codex/rules/AGENTS.md`.
- Repo instructions in `<repo>/AGENTS.md`.
- `JARVIS.md` only inside non-core target repos where Jarvis executes work.

## Conflict Resolution
When the same rule appears in multiple places:
1. Keep the most specific owner.
2. Remove duplicates from broader scopes.
3. Add a short pointer from broader scope to owner if needed.

## Update Checklist
- Confirm owner scope before editing.
- Edit only owner file(s).
- Avoid copying full policy text between scopes.
- Verify no contradictory rules remain.
- Record what changed and why in commit/task summary.

## Reference
- For canonical examples and quick mapping, read `references/context-placement-matrix.md`.

Files: 3

Size: 4.1 KB

Complexity: 19/100

Category: Writing & Docs

Source: https://github.com/ingpoc/skills/tree/main/project-context-router

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts