[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DJ0D2M8JP3K67HF3EPWRXC":3,"skill-same:01M6DJ0D2M8JP3K67HF3EPWRXC":183},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":75,"commitSha":76,"skillDirectory":77,"forksCount":78,"repositoryHtmlUrl":79,"repositoryHomepageUrl":6,"ownerHtmlUrl":80,"ownerBlogUrl":6,"ownerDescription":81,"updatedAt":82,"install":83,"resources":96},"01M6DJ0D2M8JP3K67HF3EPWRXC","sql-pro",null,"Use when someone needs help writing or rewriting SQL — authoring complex joins, CTEs, window functions, or recursive queries — or designing a schema from scratch, normalizing an existing one, or migrating queries between database dialects.","newkayak12\u002Fclaude-skills","newkayak12","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F74722411?v=4","01M6DHQRSHSVM4F2EJACTMC766","Sanghyeon Kim","01M6DHQRX6XQ0XKTD3QB8CGFM9",3,"MIT","https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Fsql-pro\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"sql","sql pro","tool","optimizer","query","functions","engineer","schema","use","strategy","spring","explain","design","sse","database","code","boot","oracle","writing","MCP","2026-11-10 10:12:30",false,"---\nname: sql-pro\ndescription: >-\n  Use when someone needs help writing or rewriting SQL — authoring complex\n  joins, CTEs, window functions, or recursive queries — or designing a schema\n  from scratch, normalizing an existing one, or migrating queries between\n  database dialects.\nscenarios:\n  - \"Rewrite this slow SQL query that's doing full table scans on a 50M row table\"\n  - \"Help me write a complex analytics query with CTEs, window functions, and aggregations\"\n  - \"Our report query takes 5 minutes — optimize it with proper indexing strategy\"\n  - \"풀 테이블 스캔을 하는 느린 쿼리를 최적화해줘\"\n  - \"윈도우 함수와 CTE를 활용한 복잡한 분석 쿼리를 작성해줘\"\ncompatibility:\n  recommended: []\n  optional:\n    - think-tool\n  remote_mcp_note: >-\n    think-tool이 있으면 쿼리 실행 계획 해석과 인덱스 전략 결정을 더 체계적으로 검토합니다.\n    Claude 설정 → MCP Servers에서 remote SSE 엔드포인트를 추가하세요.\nlicense: MIT\nmetadata:\n  version: \"1.1.0\"\n  role: specialist\n  triggers: SQL tuning, slow query, schema design, PostgreSQL, MySQL, SQL Server, Oracle, window functions, CTE, EXPLAIN plan, index design\n  scope: implementation\n  domain: language\n  related-skills: database-optimizer, connection-pool-tuner, spring-boot-engineer\n  output-format: code\n---\n\n## Standing Mandates\n\n- NEVER propose a rewrite or index before you have the execution plan and the row counts. A fix written from the query\n  text alone is a guess; the same text can be fast on 10k rows and a full scan on 50M. No plan supplied is\n  `[확인 필요: EXPLAIN ANALYZE]`, and the rewrite is marked `unmeasured`.\n- NEVER report a speedup you did not see as a before\u002Fafter number. A claimed gain without both plans is `unverified`.\n- Target engine and version unknown is `[확인 필요: engine\u002Fversion]`; never assume dialect-specific syntax is available.\n- Goal: the final query, its plan before and after, and a closing tally that recounts to the evidence lines (schema or\n  porting tasks: the DDL\u002Fquery and its caveats; plan lines read n\u002Fa).\n\n# SQL Pro\n\nWrites and rewrites SQL, designs schemas, and ports queries between dialects, judged by the plan, not by the look of the query.\n\n**Not for** server-level causes: memory, VACUUM, lock waits (`develop:database-optimizer`), pool exhaustion\n(`develop:connection-pool-tuner`), or transaction scope (`develop:transaction-boundary-reviewer`).\n\n## Process\n\n1. **Context.** Read schema, indexes, and the query; confirm engine and version. Read the repo before asking.\n2. **Design.** Shape the query as set operations: CTEs, window functions, correct join types.\n3. **Plan.** Read the `EXPLAIN` first, then optimize: covering indexes, early filters, no big sequential scans.\n4. **Verify.** Re-run `EXPLAIN ANALYZE`; compare to the baseline. Stop when the user's latency target is met (absent:\n   `[확인 필요: target latency]`) or after 3 rounds with no improvement, and report the best plan with the remaining bottleneck.\n5. **Document.** Index rationale, engine caveats, minimum version. Before sending, recount the tally against the\n   finding\u002Fchange lines; fix the header if they differ.\n\nCoding rules and worked examples (CTE, window, correlated-subquery rewrite): `references\u002Fworked-examples.md`.\n\n| Topic | File | Read it when |\n|-------|------|--------------|\n| Query shapes | `references\u002Fquery-patterns.md` | Joins, CTEs, recursion, subquery rewrites, pivots, keyset paging |\n| Analytic windows | `references\u002Fwindow-functions.md` | Ranking, running totals, LAG\u002FLEAD, frames, gaps-and-islands |\n| Tuning and plans | `references\u002Foptimization.md` | Plan reading, index choice, statistics, partitioning |\n| Schema design | `references\u002Fdatabase-design.md` | Normal forms, keys, constraints, history tables, migrations |\n| Porting engines | `references\u002Fdialect-differences.md` | PostgreSQL, MySQL, SQL Server, Oracle |\n\n## Output Template\n\n```\n## SQL — \u003Ctask>\n\nQuery: \u003Cfinal query, commented inline>\nIndexes: \u003CDDL → why>\nPlan: before \u003Ccost\u002Ftime, key node> → after \u003Ccost\u002Ftime, key node>   (or unmeasured: [확인 필요: EXPLAIN ANALYZE])\nCaveats: \u003Cengine-specific>   Minimum version: \u003Ce.g. PostgreSQL >= 10>\n\n\u003Cn> queries · \u003Cm> measured before\u002Fafter · \u003Ck> unmeasured\n```\n\n## What Claude Does \u002F What You Do\n\n| Claude | You |\n|--------|-----|\n| Writes the set-based query, reads the plan, proposes indexes | Provide schema DDL, sample data, actual `EXPLAIN ANALYZE` |\n| Flags dialect differences | Test on your DB version; run `CREATE INDEX CONCURRENTLY` yourself |\n| Writes up the before\u002Fafter | Check it against production-sized data |\n\n## Related Skills\n\n- `develop:database-optimizer` — server-level tuning after the query is optimized\n- `develop:connection-pool-tuner` — pool sizing if slow queries are exhausting connections\n- `develop:spring-boot-engineer` — JPA query methods and `@Query`\n","## Standing Mandates\n\n- NEVER propose a rewrite or index before you have the execution plan and the row counts. A fix written from the query\n  text alone is a guess; the same text can be fast on 10k rows and a full scan on 50M. No plan supplied is\n  `[확인 필요: EXPLAIN ANALYZE]`, and the rewrite is marked `unmeasured`.\n- NEVER report a speedup you did not see as a before\u002Fafter number. A claimed gain without both plans is `unverified`.\n- Target engine and version unknown is `[확인 필요: engine\u002Fversion]`; never assume dialect-specific syntax is available.\n- Goal: the final query, its plan before and after, and a closing tally that recounts to the evidence lines (schema or\n  porting tasks: the DDL\u002Fquery and its caveats; plan lines read n\u002Fa).\n\n# SQL Pro\n\nWrites and rewrites SQL, designs schemas, and ports queries between dialects, judged by the plan, not by the look of the query.\n\n**Not for** server-level causes: memory, VACUUM, lock waits (`develop:database-optimizer`), pool exhaustion\n(`develop:connection-pool-tuner`), or transaction scope (`develop:transaction-boundary-reviewer`).\n\n## Process\n\n1. **Context.** Read schema, indexes, and the query; confirm engine and version. Read the repo before asking.\n2. **Design.** Shape the query as set operations: CTEs, window functions, correct join types.\n3. **Plan.** Read the `EXPLAIN` first, then optimize: covering indexes, early filters, no big sequential scans.\n4. **Verify.** Re-run `EXPLAIN ANALYZE`; compare to the baseline. Stop when the user's latency target is met (absent:\n   `[확인 필요: target latency]`) or after 3 rounds with no improvement, and report the best plan with the remaining bottleneck.\n5. **Document.** Index rationale, engine caveats, minimum version. Before sending, recount the tally against the\n   finding\u002Fchange lines; fix the header if they differ.\n\nCoding rules and worked examples (CTE, window, correlated-subquery rewrite): `references\u002Fworked-examples.md`.\n\n| Topic | File | Read it when |\n|-------|------|--------------|\n| Query shapes | `references\u002Fquery-patterns.md` | Joins, CTEs, recursion, subquery rewrites, pivots, keyset paging |\n| Analytic windows | `references\u002Fwindow-functions.md` | Ranking, running totals, LAG\u002FLEAD, frames, gaps-and-islands |\n| Tuning and plans | `references\u002Foptimization.md` | Plan reading, index choice, statistics, partitioning |\n| Schema design | `references\u002Fdatabase-design.md` | Normal forms, keys, constraints, history tables, migrations |\n| Porting engines | `references\u002Fdialect-differences.md` | PostgreSQL, MySQL, SQL Server, Oracle |\n\n## Output Template\n\n```\n## SQL — \u003Ctask>\n\nQuery: \u003Cfinal query, commented inline>\nIndexes: \u003CDDL → why>\nPlan: before \u003Ccost\u002Ftime, key node> → after \u003Ccost\u002Ftime, key node>   (or unmeasured: [확인 필요: EXPLAIN ANALYZE])\nCaveats: \u003Cengine-specific>   Minimum version: \u003Ce.g. PostgreSQL >= 10>\n\n\u003Cn> queries · \u003Cm> measured before\u002Fafter · \u003Ck> unmeasured\n```\n\n## What Claude Does \u002F What You Do\n\n| Claude | You |\n|--------|-----|\n| Writes the set-based query, reads the plan, proposes indexes | Provide schema DDL, sample data, actual `EXPLAIN ANALYZE` |\n| Flags dialect differences | Test on your DB version; run `CREATE INDEX CONCURRENTLY` yourself |\n| Writes up the before\u002Fafter | Check it against production-sized data |\n\n## Related Skills\n\n- `develop:database-optimizer` — server-level tuning after the query is optimized\n- `develop:connection-pool-tuner` — pool sizing if slow queries are exhausting connections\n- `develop:spring-boot-engineer` — JPA query methods and `@Query`\n",{"name":5,"license":15,"metadata":57,"scenarios":64,"description":7,"compatibility":70},{"role":58,"scope":59,"domain":60,"version":61,"triggers":62,"output-format":47,"related-skills":63},"specialist","implementation","language","1.1.0","SQL tuning, slow query, schema design, PostgreSQL, MySQL, SQL Server, Oracle, window functions, CTE, EXPLAIN plan, index design","database-optimizer, connection-pool-tuner, spring-boot-engineer",[65,66,67,68,69],"Rewrite this slow SQL query that's doing full table scans on a 50M row table","Help me write a complex analytics query with CTEs, window functions, and aggregations","Our report query takes 5 minutes — optimize it with proper indexing strategy","풀 테이블 스캔을 하는 느린 쿼리를 최적화해줘","윈도우 함수와 CTE를 활용한 복잡한 분석 쿼리를 작성해줘",{"optional":71,"recommended":73,"remote_mcp_note":74},[72],"think-tool",[],"think-tool이 있으면 쿼리 실행 계획 해석과 인덱스 전략 결정을 더 체계적으로 검토합니다. Claude 설정 → MCP Servers에서 remote SSE 엔드포인트를 추가하세요.","main","cdb89e1460a1035ae4d122ee0b33344216b2cbfe","develop\u002Fskills\u002Fsql-pro",1,"https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Fnewkayak12","그냥 하는 사람\r\n","2026-11-11 21:29:03",{"source":8,"skillName":5,"commands":84,"prompt":94,"zipAvailable":95},[85,88,91],{"tool":86,"command":87},"npx","npx skills add newkayak12\u002Fclaude-skills --skill sql-pro",{"tool":89,"command":90},"bunx","bunx skills add newkayak12\u002Fclaude-skills --skill sql-pro",{"tool":92,"command":93},"pnpm","pnpm dlx skills add newkayak12\u002Fclaude-skills --skill sql-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Fsql-pro\u002FSKILL.md",true,[97,103,107,111,115,119,123,127,131,135,139,143,147,151,155,159,163,167,171,175,179],{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"README.md","REFERENCE","参考文档",3218,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002FREADME.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fadvanced-gis.md",10745,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fadvanced-gis.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fbig-data.md",8455,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fbig-data.md",{"path":112,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fcode-examples.md",12492,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fcode-examples.md",{"path":116,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fcoordinate-systems.md",8893,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fcoordinate-systems.md",{"path":120,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fcore-libraries.md",6593,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fcore-libraries.md",{"path":124,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Fdata-sources.md",9001,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fdata-sources.md",{"path":128,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":129,"sourceHtmlUrl":130},"references\u002Fdatabase-design.md",4506,"https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Fsql-pro\u002Freferences\u002Fdatabase-design.md",{"path":132,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":133,"sourceHtmlUrl":134},"references\u002Fdialect-differences.md",5895,"https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Fsql-pro\u002Freferences\u002Fdialect-differences.md",{"path":136,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":137,"sourceHtmlUrl":138},"references\u002Fgis-software.md",8915,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fgis-software.md",{"path":140,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":141,"sourceHtmlUrl":142},"references\u002Findustry-applications.md",13071,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Findustry-applications.md",{"path":144,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":145,"sourceHtmlUrl":146},"references\u002Fmachine-learning.md",12783,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fmachine-learning.md",{"path":148,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":149,"sourceHtmlUrl":150},"references\u002Foptimization.md",6385,"https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Fsql-pro\u002Freferences\u002Foptimization.md",{"path":152,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":153,"sourceHtmlUrl":154},"references\u002Fprogramming-languages.md",11024,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fprogramming-languages.md",{"path":156,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":157,"sourceHtmlUrl":158},"references\u002Fquery-patterns.md",4571,"https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Fsql-pro\u002Freferences\u002Fquery-patterns.md",{"path":160,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":161,"sourceHtmlUrl":162},"references\u002Fremote-sensing.md",10104,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fremote-sensing.md",{"path":164,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":165,"sourceHtmlUrl":166},"references\u002Fscientific-domains.md",10611,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fscientific-domains.md",{"path":168,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":169,"sourceHtmlUrl":170},"references\u002Fspecialized-topics.md",10686,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Fspecialized-topics.md",{"path":172,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":173,"sourceHtmlUrl":174},"references\u002Ftroubleshooting.md",11219,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fgeomaster\u002Freferences\u002Ftroubleshooting.md",{"path":176,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":177,"sourceHtmlUrl":178},"references\u002Fwindow-functions.md",4359,"https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Fsql-pro\u002Freferences\u002Fwindow-functions.md",{"path":180,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":181,"sourceHtmlUrl":182},"references\u002Fworked-examples.md",1600,"https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Fsql-pro\u002Freferences\u002Fworked-examples.md",[184,207,232,253,272,293],{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":52},"01M6DJ9KATAGNQ28QRQWG32PNG","diagram","Use when something must be drawn as a checked figure, not Mermaid: page layout, B-tree, lock timeline, ER, benchmark chart, architecture, sequence. SVG + PNG. Triggers: \"도식화해줘\", \"그림으로 그려줘\", \"책에 넣을 그림\", \"시퀀스 다이어그램\", \"draw this as a figure\".","https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fwrite\u002Fskills\u002Fdiagram\u002FSKILL.md",[],[186,191,192,193,194,195,196,197,198,34,199,40,200,201,36,202,203,204,205,206],"web","architecture","mermaid","browser","cache","redis","api","b-tree","page","er","postgres","layout","triggers","as","chart","SVG",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":217,"publishedAt":52},"01M6DJ0RNQFTMCJFZ0F90TKV6X","test-master","Use when writing, improving, or auditing tests, or writing case specs with expected results from a spec. Triggers: \"테스트 작성\", \"테스트 케이스 작성\", \"test case writing\", \"단위 테스트\", \"커버리지 분석\", \"test plan\", \"defect report\".","https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Ftest-master\u002FSKILL.md",[213,216],{"categoryNo":214,"categoryName":215,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[218,219,220,221,51,50,222,223,224,45,225,226,34,227,228,40,229,230,231,203],"test","master","test master","testing","unit tests","development","qa","test plan","plan","analyze","coverage","only","thinking","tests",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":239,"publishedAt":52},"01M6DJ0HNBTK0C266899VBY25J","sre-engineer","Use when setting up production reliability practices. Triggers on: \"SLO 정하고 싶어\", \"에러 버짓\", \"알람 피로\", \"반복 작업(toil) 줄이기\", \"golden signals dashboard\", \"burn-rate alert\". Not for active incidents or chaos tests.","https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Fsre-engineer\u002FSKILL.md",[238],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[240,38,241,51,242,243,34,244,40,245,246,247,248,249,250,230,251,252,231,203],"sre","sre engineer","observability","SET","fix","reliability","slo","sli","burn-rate","alert","up","call","define",{"skillNo":254,"name":255,"nameZh":6,"description":256,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":257,"categories":258,"keywords":264,"publishedAt":52},"01M6DJ07ZKVJXBHFF6F1KE8SF9","spring-boot-engineer","Use when building or extending a Spring Boot 3.x Java backend — REST, Spring Security, JPA, WebFlux, Actuator. Triggers on: \"Spring Boot API\", \"스프링 시큐리티 설정\", \"JPA 연동\". Not for service decomposition or query tuning.","https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Fspring-boot-engineer\u002FSKILL.md",[259,260,261],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":262,"categoryName":263,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师",[48,265,42,38,266,51,192,47,267,46,268,197,269,34,270,40,36,271,35,203],"spring boot","spring boot engineer","authentication","java","configure","kotlin","caching",{"skillNo":273,"name":274,"nameZh":6,"description":275,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":276,"categories":277,"keywords":279,"publishedAt":52},"01M6DJ036MK4ESPPFEY6WY8FWZ","spec-driven-development","Use when a feature should be specified before it is coded — stories, acceptance criteria, tasks, a per-criterion check. Triggers: \"스펙 먼저\", \"명세부터 쓰고 구현\", \"수용 기준 먼저\", \"spec first\", \"spec-driven development\".","https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Fspec-driven-development\u002FSKILL.md",[278],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[280,281,223,282,283,51,284,285,286,287,45,34,288,40,289,290,230,291,292,203],"spec","spec driven development","spec driven","driven","implement","tasks","acceptance","first","write","think","do","acceptance criteria","feature",{"skillNo":294,"name":295,"nameZh":6,"description":296,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":297,"categories":298,"keywords":301,"publishedAt":52},"01M6DHYFTQSA9RQ6YXNDHF0N4J","like-my-code","Use when a repo's code style must become written policy — harness conventions (coding.md, boundaries.md) backed by repo evidence. Triggers: \"내 코드 스타일로 컨벤션 뽑아줘\", \"이 레포 스타일을 정책으로\", \"like my code\", \"extract conventions from this repo\".","https:\u002F\u002Fgithub.com\u002Fnewkayak12\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fdevelop\u002Fskills\u002Flike-my-code\u002FSKILL.md",[299,300],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":262,"categoryName":263,"taxonomyType":29,"taxonomyTypeDesc":30},[47,302,51,303,304,305,197,45,34,306,307,308,309,40,310,289,311,203,312],"like my code","policy","code style","harness","coding","work","repo","extract","evidence","conventions","style"]