update-how-it-works

To update feature documentation, map the implementation changes to the correct how-it-works file, preserving one document per feature. This ensures concise, feature-scoped documentation for current code paths stays aligned with the codebase.

The best way to keep how-it-works docs aligned is refreshing the corresponding documentation entry immediately after changing a component. This explains the current system, key files, and main flow so engineers avoid reverse-engineering behavior from stale notes.

You need to refresh feature-scoped technical writing when a feature changes its behavior, architecture, rendering, or interaction logic. This keeps the repository documentation index in sync and provides compact engineering guidance for current code paths.

Yes, this documentation synchronization method maps code changes to the right document instead of rewriting unrelated documentation. It maps implementation changes to the correct how-it-works files, preserving one document per feature.

Yes, you can use this approach to update documentation for components in pattern-studio and related OpenSpec-backed features. It applies to engineering workflows needing concise documentation for current code paths in apps/web/src/components/pattern-studio.