Skip to content

shinpr/claude-code-workflows / dev-skills/skills/external-resource-context

external-resource-context

Verified

Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the user mentions design source, design system, API schema, IaC source, secret store, or canonical source.

FileKindSize
SKILL.mdskill md4.4 KB
references/api.mdmarkdown690 B
references/backend.mdmarkdown704 B
references/frontend.mdmarkdown714 B
references/hearing.mdmarkdown1.8 KB
references/infra.mdmarkdown690 B
references/template.mdmarkdown1.1 KB

references/hearing.md

View on GitHub
# External Resource Capture

Capture a resource only when repository and supplied evidence cannot decide a current design, implementation or verification question without it. Absence of a project record does not trigger a domain-wide questionnaire.

## Resolve Access

1. Name the decision and required external fact. Read the existing project entry and feature identifier when available.
2. Reuse access details from the user, governing artifacts or repository configuration. Fetch the selected content within current authority. A new record can be written from this evidence without a hearing.
3. Ask only for a missing location, access method or user-owned interpretation that prevents the decision. The calling workflow owns interaction; an autonomous consumer returns the exact missing evidence to that caller and continues independent work.
4. Correct stale details when authoritative current evidence establishes the replacement. When it does not, preserve the last known record, report the failed access and ask only for the unresolved decision-relevant fact. Record locations and access mechanisms, never secret values.

## Optional Domain Cues

Load only the reference needed to locate the selected fact: [frontend.md](frontend.md), [backend.md](backend.md), [api.md](api.md), or [infra.md](infra.md). Their lists are cues, not required questions or completion axes.

## Store

Use [template.md](template.md) for `docs/project-context/external-resources.md`. Keep environment facts at project level and feature-specific identifiers in the consuming document's `External Resources Used` table. Preserve unrelated entries and stable labels. Create no empty record or N/A catalog when no external source is required. Return changed paths and any exact remaining evidence limitation to the caller.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall