All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed
ACQUIRE reverse-engineering/SKILL.md FROM KB — apply "Would we rebuild this?" test: pattern = recurring structure surviving a from-scratch rewrite; one-off = historical accident
Pattern qualifies only if found in 2+ places
INDEX.md and CHANGES.md must be possible to grep by md headers (top 3 levels). Must not use tables. Instructions ask to grep files to populate list of those items in context.
Read CODEMAP.md — scope extraction per module
if not enough use shell to list recursively all files with minimal output parameters
limit top 10-15 most common patterns
limit reading samples to 2-3 files per pattern
add 2-3 more patterns as you see fit
Dual-mode:
CHECK-EXISTS: read docs/PATTERNS/ and INDEX.md
IDENTIFY-GAPS: compare existing patterns against codebase
CREATE-OR-UPDATE: install = create all; upgrade = add missing only
PRESERVE-HUMAN: never overwrite human-curated content
REPORT-CHANGES: log to CHANGES.md
Per pattern file (docs/PATTERNS/*.md):
Name: short identifier (e.g., "REST Controller Endpoint")
Description: what it solves, when to use
Template/Example: generalizable code skeleton with extension-point comments
Write docs/PATTERNS/INDEX.md — all patterns with one-line descriptions, one header per each pattern ## Pattern Name - short description
Write docs/PATTERNS/CHANGES.md — created/updated/skipped, one header per each change ## [YYYY-MM-DD] Brief changes made
If state.composite = true, extract per sub-repository; top-level INDEX.md references sub-repo folders
1---2name: init-workspace-patterns3description: Extract code patterns.4license: Apache-2.05---67<init_workspace_patterns>89<role>10Senior pattern architect — recovers reusable structural conventions from code.11</role>1213<when_to_use_skill>14Codebases accumulate implicit recurring structures that drift without formal documentation. Extract them into explicit reusable templates so agents and contributors produce consistent code. Requires CODEMAP.md on disk.15</when_to_use_skill>1617<core_concepts>1819- All Rosetta prep steps MUST be FULLY completed, load-context skill loaded and fully executed20- ACQUIRE `reverse-engineering/SKILL.md` FROM KB — apply "Would we rebuild this?" test: pattern = recurring structure surviving a from-scratch rewrite; one-off = historical accident21- Pattern qualifies only if found in 2+ places22- INDEX.md and CHANGES.md must be possible to grep by md headers (top 3 levels). Must not use tables. Instructions ask to grep files to populate list of those items in context.2324</core_concepts>2526<process>27281. Read CODEMAP.md — scope extraction per module29 - if not enough use shell to list recursively all files with minimal output parameters30 - limit top 10-15 most common patterns31 - limit reading samples to 2-3 files per pattern32 - add 2-3 more patterns as you see fit332. Dual-mode:34 - CHECK-EXISTS: read docs/PATTERNS/ and INDEX.md35 - IDENTIFY-GAPS: compare existing patterns against codebase36 - CREATE-OR-UPDATE: install = create all; upgrade = add missing only37 - PRESERVE-HUMAN: never overwrite human-curated content38 - REPORT-CHANGES: log to CHANGES.md393. Per pattern file (docs/PATTERNS/*.md):40 - **Name**: short identifier (e.g., "REST Controller Endpoint")41 - **Description**: what it solves, when to use42 - **Template/Example**: generalizable code skeleton with extension-point comments434. Write docs/PATTERNS/INDEX.md — all patterns with one-line descriptions, one header per each pattern `## Pattern Name - short description`445. Write docs/PATTERNS/CHANGES.md — created/updated/skipped, one header per each change `## [YYYY-MM-DD] Brief changes made`456. If state.composite = true, extract per sub-repository; top-level INDEX.md references sub-repo folders4647</process>4849<validation_checklist>50- Every pattern represents a genuinely recurring structure (2+ occurrences)51- INDEX.md lists all pattern files52- CHANGES.md tracks all actions taken53- No human-curated content overwritten in upgrade mode54</validation_checklist>5556</init_workspace_patterns>
Run npx skillmds@latest add griddynamics/init-workspace-patterns in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Extract code patterns. It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.
griddynamics (@griddynamics) published this skill. Their other Agent Skills are listed on their SkillMD profile.
griddynamics