Project context adapter
Skill ytvee-dev/webdev-agent-kit/skills/project-context-adapter
Refresh local-only project/** facts and frontend path indexes after stack, routing, styling, asset, verification, docs/tool, design-reference, pattern, or ownership changes. Do not put project facts in reusable skills.From its SKILL.md
npx -y skills add ytvee-dev/webdev-agent-kit --skill project-context-adapterAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
6.1 KB, 952 tokens by cl100k_base, as published. Nobody here has run it
Project Context Adapter
Purpose
Refresh factual host-project context in project/** so reusable skills can
implement screenshot-derived specs without scanning the whole repository.
When To Use
- Project structure, routes, entrypoints, styling systems, assets, or verification commands changed.
- A new frontend stack fact was discovered during implementation.
- Current skill capability declarations, available providers, or official documentation choices changed.
- Design-reference boundaries, approved patterns, or anti-patterns changed.
- Path indexes no longer match actual source files.
When Not To Use
- First-time full onboarding in Plan Mode. Use
project-onboarding-adapter. - Reusable skill authoring. Use
agent-rules-skill-author. - Screenshot spec writing or implementation unless project facts changed.
Required Context
- Read
AGENTS.md. - Confirm the classified task is
project-context-refreshor a project context cache update required by another task. - Read
common/documentation-maintenance.md. - Read existing
project/**overlays. - Inspect relevant manifests, configs, entrypoints, routes, components,
styles, assets,
tool-capabilities-manifest.json, and verification scripts. - Read
references/extraction-checklist.md. - Read
references/sync-procedure.md.
Read targeted README sections only when the refresh concerns project intent, setup guidance, or documentation drift. Use common/readme-policy.md and confirm cached technical facts through higher evidence.
Tool Contract
- Use Project Context MCP when available.
- Use filesystem reads and targeted search when Project Context MCP is unavailable.
- Use
context7and MDN only when refreshing official documentation choices or stack-specific pattern notes that depend on current external docs. - Activate
openai_platform_docsonly when refreshed project facts depend on current OpenAI or Codex behavior. - Do not use Figma MCP.
- Edit only
project/**unless the user also requests bundle skill or policy changes.
Workflow
- Determine which project facts changed.
- Update only affected overlays or path indexes.
- Refresh
project/mcp-profile.mdwhen skill capabilities, validated providers servers, official docs choices, or verification capabilities changed. - Refresh
project/design-reference-profile.mdwhen screenshot, exported asset, copied inspect, or design-source boundaries changed. - Refresh
project/approved-patterns.mdandproject/anti-patterns.mdonly from real project code or official documentation for the detected stack. - Keep graph frontmatter current with
publishable: falseandlocal_only: true. - Keep host-project facts out of
AGENTS.md,README.md,common/**, manifests, and reusableskills/**. - Verify updated facts against actual files or official documentation sources.
Output Contract
Final response: return only facts that affect the user's understanding, confidence, or next action. Omit empty fields and workflow narration.
Report:
- overlays updated;
- source facts used;
- official documentation or MCP facts refreshed;
- project paths indexed or changed;
- verification performed;
- any project facts that remain unknown.
Validation Gates
project/**files must remain local-only.- Path indexes must point to existing files or explicitly mark missing owners.
project/mcp-profile.mdmust match active declarations intool-capabilities-manifest.jsonwhen it is touched; provider config alone must not be recorded as availability.project/design-reference-profile.mdmust not imply live design-tool access.- Patterns and anti-patterns must cite real local code facts or official documentation choices, not generic preferences.
- Reusable skills must not receive host-specific facts.
- README claims must not become project facts without confirmation from source, config, CI, package scripts, lockfiles, official documentation, or real results.
- Context refresh must not edit README unless the current user explicitly requests that README change.
- No Figma MCP or Figma whiteboard workflow may be introduced.
Trigger Evals
Should trigger:
- "Refresh project context after this layout change."
- "Update .agents/project path indexes."
- "The styling profile is stale; sync it with the repo."
Should not trigger:
- "Create a design implementation spec from screenshots."
- "Implement this screen."
- "Plan first-time onboarding for a new project."
Reference Map
references/extraction-checklist.mdreferences/sync-procedure.mdcommon/readme-policy.md
What ships with it: 3 files
3.6 KB alongside SKILL.md
agents/
- openai.yaml300 B
references/
- extraction-checklist.md1.5 KB
- sync-procedure.md1.8 KB
Gives 0 of the 12 instructions most design frontend skills give in 952 tokens
Counted across 1,179 of the 2,086 authors here whose files we hold, read 2026-09-06
- Commit to a bold aesthetic directionin 31 of 1179, across 24 files
- Prefer component composition over inheritancein 28 of 1179, across 14 files
- Animate only transform and opacity propertiesin 27 of 1179, across 22 files
- Memoize expensive computations with useMemoin 26 of 1179, across 13 files
- Use semantic HTML elementsin 24 of 1179, across 23 files
- Virtualize long lists for performancein 21 of 1179, across 10 files
- Use CSS variables for design tokensin 20 of 1179, across 14 files
- Implement loading, empty, and error statesin 20 of 1179
- Lazy load heavy components with Suspensein 19 of 1179, across 8 files
- Respect prefers-reduced-motion media queriesin 18 of 1179, across 10 files
- Prioritize CSS-only animations for HTMLin 18 of 1179, across 16 files
- Use compound components for related UI elementsin 18 of 1179, across 7 files
Said here and by no other author read
- read project context files and relevant manifests
- update only affected overlays or path indexes
- refresh project profile files when capabilities change
- verify updated facts against actual files
- keep graph frontmatter local only
- cite real code facts for patterns and anti-patterns
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.