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/template.md

View on GitHub
# Storage Templates

## Project Record

Path: `docs/project-context/external-resources.md`. Preserve existing resource labels referenced by feature documents. Include only resources actually needed; adapt grouping to the existing file.

```markdown
# External Resources

## [Stable resource label]
- Purpose: [decision or contract served]
- Location: [URL, path, package or service]
- Access method: [read operation, tool or command within existing authority]
- Evidence: [source and relevant version/date]
```

Keep credentials and secret values outside this record. Record an access limitation when it affects a consumer; a failed fetch does not establish that the resource is absent.

## Feature Reference

Use the consuming document's natural heading level for `External Resources Used`.

```markdown
## External Resources Used

| Project resource label | Feature-specific identifier | Use |
|---|---|---|
| [existing label] | [node, endpoint, module or version selector] | [decision or proof] |
```

Project entries own shared locations and access methods; feature rows own only the subset and identifiers used here.
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: 468kUpdated 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: 468kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 468kUpdated 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