Skill: /update-references

Usage

/update-references
/update-references auto
/update-references laravel
/update-references react
/update-references react-native
/update-references frontend
/update-references all

auto is the default and preferred mode.

Why this step matters

The files in references/ are the project's durable AI map.

If code changes but the maps do not, future tasks will:

• look for files that no longer exist
• miss newly introduced files or flows
• rely on outdated method names, props, services, routes, or tables
• waste tokens repeatedly rediscovering structure that should already be mapped

Core rules

1. Reference-first. Read the existing applicable maps before updating them.
2. Use the current task as the source of truth. Inspect the changed files in the current working tree, staged set, or explicitly touched files for this task. Do not rely on main~1..main assumptions.
3. Update only the affected maps. Do not rewrite unrelated sections.
4. Inspect the changed code directly. Refresh the map from the real files, not from memory.
5. Treat absent maps as not applicable. Do not create a mobile map for a repo that has no mobile app.

Update workflow

1. Discover what changed

Preferred sources, in order:

1. the files changed in the current working tree
2. staged files
3. the files explicitly modified during the task

If the repo uses git, use the current worktree state rather than merge-based history. Include tracked and untracked files when relevant.

If git is unavailable, use the files touched in this session or the files named in the approved plan.

2. Load the existing maps first

Read the applicable existing maps in references/ before editing them.

• references/schema.md when database or backend changes are involved
• references/backend_map.md when Laravel/backend changes are involved
• references/frontend_map.md when React or frontend changes are involved
• references/mobile_map.md when React Native/mobile changes are involved
• references/methodology.md when the task introduced a new convention, architecture rule, or working pattern

3. Infer scope in auto mode

Map changed files to reference files conservatively:

• migrations or schema files → references/schema.md
• Laravel routes, controllers, services, models, policies, jobs, resources, requests, middleware → references/backend_map.md
• React/frontend pages, components, hooks, stores, services, routing, shared types → references/frontend_map.md
• React Native screens, navigation, Expo/native config, mobile services, platform-specific files → references/mobile_map.md
• new architectural or naming patterns → references/methodology.md

If unsure, update the narrower relevant map and add [REVIEW NEEDED] rather than fabricating certainty.

4. Refresh each affected map

references/schema.md

Update tables, columns, constraints, defaults, and relations introduced by the changed schema files.

references/backend_map.md

Update route flows, controllers, services, repositories, models, auth, middleware, queues, resources, and known gotchas that changed.

references/frontend_map.md

Update routing, pages, components, hooks, stores, services, API config, and key types/interfaces that changed.

references/mobile_map.md

Update app roots, navigation, screens, services, storage/auth behavior, platform-specific notes, Expo/native config, and build notes that changed.

references/methodology.md

Only update when the task introduced a genuine new pattern or convention that future tasks need to follow.

5. No-op handling

If the changed files are docs-only, planning-only, or otherwise irrelevant to the project maps, report a no-op and do not modify references/.

6. Completion report

Report exactly which files were updated.

Use this format:

REFERENCE FILES UPDATED
  references/schema.md        -> updated | skipped | not applicable
  references/backend_map.md   -> updated | skipped | not applicable
  references/frontend_map.md  -> updated | skipped | not applicable
  references/mobile_map.md    -> updated | skipped | not applicable
  references/methodology.md   -> updated | skipped | not applicable

End with:

/update-references complete
references/ is now aligned with the current code changes.