update-skills

You can preserve session learnings by capturing significant patterns, pitfalls, and domain knowledge as reusable skills. This formalizes discoveries into an instruction set with structured frontmatter, ensuring knowledge persists across future coding sessions instead of being lost.

Documenting repository patterns and pitfalls is best handled by converting them into structured skills or instructions. This approach enforces a consistent frontmatter with name and description, making repository knowledge formalized and discoverable for future reference.

Capturing major learnings as skills reduces repeated debugging by creating a persistent knowledge base. When significant domain knowledge or pitfalls are formalized into instructions, future sessions can reference them to avoid encountering the same issues.

Yes, you can attach optional assets such as scripts and references when you save a learning. This extensibility allows you to provide extended context alongside the required frontmatter, ensuring the captured skill has all necessary supporting materials.

Yes, every captured learning requires a frontmatter structure that enforces both a name and description. This mandatory metadata ensures the skill remains discoverable and can be properly loaded by the system during future sessions.

You should formalize a session discovery into a reusable skill when major learnings are identified, such as uncovering significant patterns, domain knowledge, or pitfalls. If the insight is valuable enough to persist across future sessions, it warrants formalization.