Skip to content
Back to skills

Design Evolve

ASecurity

Use when integrating supplied discussions or decisions into a self-contained next version of existing design documents.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 15, 2026
business

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 15, 2026

npx -y skills add MVPavan/via --skill design-evolve --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Design Evolve?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Design Evolve
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mvpavan-design-evolve/badge)](https://www.skillsdirectory.com/skills/mvpavan-design-evolve)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: design-evolve
description: Use when integrating supplied discussions or decisions into a self-contained next version of existing design documents.
---

# Design Evolve

Integrate authorized decisions into a complete next version of design documents,
preserving source precision and invariants. Integration does not authorize redesign.

1. Resolve source version, target identifier/path and included discussion files
   from the request. Use supplied paths without reconfirmation; ask only about
   missing material scope or whether existing target content may be overwritten.
2. Inventory source core and discussions. Group changes by concept and identify
   authoritative decisions versus proposals, scratchpads and unresolved conflicts.
   Read incrementally; delegate bounded independent reads only when beneficial.
3. For each concept, read the actual discussion and affected core sections before
   editing. A summary guides navigation but is not sufficient evidence for a
   consequential change. Record source → target section → intended change.
4. Start each target document from its complete source. Integrate only supported
   decisions; preserve exact identifiers, numbers, error behavior and invariants
   unless explicitly superseded. Keep ambiguous choices unresolved and continue
   independent integrations while asking about material conflicts.
5. Update version headers, filenames and internal references. Copy untouched core
   files too. The target must stand alone; prior-version references belong only
   in history/provenance, not as a substitute for current design content.
6. Check cross-document consistency, section links, invariant coverage and stale
   version references. Consolidate routine duplication while preserving distinct
   context; ask only when consolidation would change meaning or authority.

Use `references/integration.md` for large-set mechanics and an optional handoff
shape. No file-size threshold or per-file agent quota applies. Report integrated
concepts, files, decisions and deferred items with source pointers. Do not label
unresolved scratchpad proposals as approved design.

Files in this skill

  • SKILL.md2.1 KB
  • agents/openai.yaml42 B
  • references/integration.md1.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.