conventions 플러그인
conventions 플러그인 설치 방법
두 명령을 모두 Claude Code 안에서 실행하십시오. 첫 번째는 마켓플레이스를 한 번 추가하고, 두 번째는 플러그인을 설치합니다.
/plugin marketplace add Powercademy/powercademy-skills
/plugin install conventions@powercademy-skillsconventions 구성 요소
플러그인 파일에서 읽어온 6개의 항목입니다.
Skills 6
작업이 일치하면 Claude가 로드합니다- dataverse-conventions
Apply Powercademy's Dataverse and Power Platform conventions before creating or changing schema - tables, columns, choices, record status, relationships, solutions, publishers - so established judgement is applied and known mistakes are not repeated. Trigger before any Dataverse schema work: "create a table", "add a column", "new choice column", "status field", "statecode", "status reason", "set up a solution", "which publisher", "add to solution", "import failed", "missing dependency", or any Power Platform / Dynamics 365 build or review touching schema, solutions, or ALM packaging - even when nobody says "best practice". Also trigger when a new convention is agreed or a mistake is corrected during Power Platform work, so the lesson gets recorded. Each entry carries its reasoning, so you can tell when it applies and when an exception is justified. If the task creates or changes Dataverse components, trigger. When in doubt, trigger.
- flow-conventions
Apply Powercademy's Power Automate lessons before building, editing or debugging a cloud flow - whichever tool does the building - so known traps are avoided rather than rediscovered. This skill holds the accumulated flow gotchas log: editing flows that already run (renames, child-flow contracts, blast radius, regression checks), designer quirks (255-character descriptions, nesting), expressions, Parse JSON, HTTP and Microsoft Graph permissions, child flow patterns, environment variables and ALM, testing when a dependency is unavailable (mocks, write gates, dry-run guards) and anti-patterns. Trigger alongside any flow work: "build a flow", "edit this flow", "add a step to my flow", "why did my flow fail", "child flow", "Parse JSON", "flow expression", "Graph call from a flow", "test this flow without the real system". It does not build flows itself - apply it, then carry on with the build tool. Also trigger when a flow lesson is learned or a mistake corrected, so it gets recorded. When in doubt, trigger.
- model-driven-ux
Apply Powercademy's UX conventions to model-driven apps, forms, command bars, dialogs and custom or generative pages, so apps feel finished and users can act without guessing. Holds the rules for command bar buttons built in the command designer - every button has an icon that says what it does, paired actions get paired icons, no icon reused for different actions on one bar, label, tooltip and accessibility text set - and for focused-task dialogs being modal. Trigger whenever the user is designing or reviewing a model-driven app's look and behaviour: "add a button", "command bar", "command designer", "ribbon", "button icon", "which icon", "Icon is required", "new command", "custom page", "generative page", "dialog", "popup", "modal", "form layout", "make the app look better", "review my app's UX". Also trigger when building commands or pages with Microsoft's tooling, and when a new UX lesson is learned, so it gets recorded. When in doubt, trigger.
- pcf-conventions
Apply Powercademy's PCF judgement before building, deploying or debugging a Power Apps component framework (PCF) code component - whichever tool builds it - starting with whether PCF is even the right tool. Holds the decision gate (out-of-the-box, canvas component or generative page first), the control-type choice (field, dataset, virtual React) and the PCF gotchas log: version bump or the cached bundle keeps rendering, dev push is not ALM, manifest binding, lifecycle traps, the harness is not the real host, the premium-licensing trap, bundle weight. Trigger alongside any PCF work: "build a PCF control", "code component", "custom control", "dataset control", "ControlManifest", "pac pcf push", "my control won't update", "works in the harness but not on the form", "does this make my app premium". It does not build controls - apply it, then carry on with the build tool. Also trigger when a PCF lesson is learned, so it gets recorded. When in doubt, trigger.
- tool-selection
Pick the right tool for each Power Platform task before acting - purpose-built plugin tools and MCP servers first, then the Dataverse SDK, Web API or pac CLI, and browser automation (Playwright) only for what has no API - and never tell the user something can't be done while browser automation could do it. Prevents the two failure modes: driving the maker portal through a browser for work an SDK does in one call (slow, brittle, costly), and refusing work that only the UI can do. Trigger whenever several tools could do the job: "use Playwright", "open the browser", "click through the portal", "is there an API for this", "bulk update records", "load this data", "create these columns", "change this setting", "check it looks right", "why is this so slow", "can you do this", and before saying any Power Platform task is impossible. Also trigger when browser automation is about to be used for data, schema, solution or flow work. When in doubt, trigger.
- writing-skills
This skill holds the Powercademy Skills house standard and the lint-enforced constraints that CI rejects violations of - dual-runtime portability rules, description limits, path conventions, the mechanics quarantine, redaction policy. Reviewing or authoring a marketplace skill without loading it will miss enforced constraints and fail CI. Trigger whenever the user says "write a skill", "new skill", "create a plugin", "add a skill to the marketplace", "review this SKILL.md", "review my skill", "improve this trigger description", "why isn't my skill triggering", or mentions a SKILL.md file, a trigger description, a skill description, authoring or reviewing an agent skill, or a skills marketplace in any way. Also trigger before authoring any SKILL.md, when editing a trigger description, or when promoting lessons from a private checklist into public skills. If the task is creating, modifying, reviewing, or structuring agent skills or plugins, trigger. When in doubt, trigger.
Claude Code에서 conventions 사용하기
Skills는 명령어가 필요하지 않습니다. 요청이 설명과 일치하면 Claude가 이를 읽습니다.
업데이트, 비활성화 또는 삭제
- 플러그인 업데이트 (shell)
- claude plugin update conventions@powercademy-skills
- marketplace 새로고침
- /plugin marketplace update powercademy-skills
- 일시적으로 비활성화
- /plugin disable conventions@powercademy-skills
- 삭제
- /plugin uninstall conventions@powercademy-skills
conventions의 스킬
- dataverse-conventionsPowercademy/powercademy-skills
Apply Powercademy's Dataverse and Power Platform conventions before creating or changing schema - tables, columns, choices, record status, relationships, solutions, publishers - so established judgement is applied and known mistakes are not repeated. Trigger before any Dataverse schema work: "create a table", "add a column", "new choice column", "status field", "statecode", "status reason", "set up a solution", "which publisher", "add to solution", "import failed", "missing dependency", or any Power Platform / Dynamics 365 build or review touching schema, solutions, or ALM packaging - even when nobody says "best practice". Also trigger when a new convention is agreed or a mistake is corrected during Power Platform work, so the lesson gets recorded. Each entry carries its reasoning, so you can tell when it applies and when an exception is justified. If the task creates or changes Dataverse components, trigger. When in doubt, trigger.
8스타 - flow-conventionsPowercademy/powercademy-skills
Apply Powercademy's Power Automate lessons before building, editing or debugging a cloud flow - whichever tool does the building - so known traps are avoided rather than rediscovered. This skill holds the accumulated flow gotchas log: editing flows that already run (renames, child-flow contracts, blast radius, regression checks), designer quirks (255-character descriptions, nesting), expressions, Parse JSON, HTTP and Microsoft Graph permissions, child flow patterns, environment variables and ALM, testing when a dependency is unavailable (mocks, write gates, dry-run guards) and anti-patterns. Trigger alongside any flow work: "build a flow", "edit this flow", "add a step to my flow", "why did my flow fail", "child flow", "Parse JSON", "flow expression", "Graph call from a flow", "test this flow without the real system". It does not build flows itself - apply it, then carry on with the build tool. Also trigger when a flow lesson is learned or a mistake corrected, so it gets recorded. When in doubt, trigger.
8스타 - model-driven-uxPowercademy/powercademy-skills
Apply Powercademy's UX conventions to model-driven apps, forms, command bars, dialogs and custom or generative pages, so apps feel finished and users can act without guessing. Holds the rules for command bar buttons built in the command designer - every button has an icon that says what it does, paired actions get paired icons, no icon reused for different actions on one bar, label, tooltip and accessibility text set - and for focused-task dialogs being modal. Trigger whenever the user is designing or reviewing a model-driven app's look and behaviour: "add a button", "command bar", "command designer", "ribbon", "button icon", "which icon", "Icon is required", "new command", "custom page", "generative page", "dialog", "popup", "modal", "form layout", "make the app look better", "review my app's UX". Also trigger when building commands or pages with Microsoft's tooling, and when a new UX lesson is learned, so it gets recorded. When in doubt, trigger.
8스타 - pcf-conventionsPowercademy/powercademy-skills
Apply Powercademy's PCF judgement before building, deploying or debugging a Power Apps component framework (PCF) code component - whichever tool builds it - starting with whether PCF is even the right tool. Holds the decision gate (out-of-the-box, canvas component or generative page first), the control-type choice (field, dataset, virtual React) and the PCF gotchas log: version bump or the cached bundle keeps rendering, dev push is not ALM, manifest binding, lifecycle traps, the harness is not the real host, the premium-licensing trap, bundle weight. Trigger alongside any PCF work: "build a PCF control", "code component", "custom control", "dataset control", "ControlManifest", "pac pcf push", "my control won't update", "works in the harness but not on the form", "does this make my app premium". It does not build controls - apply it, then carry on with the build tool. Also trigger when a PCF lesson is learned, so it gets recorded. When in doubt, trigger.
8스타 - tool-selectionPowercademy/powercademy-skills
Pick the right tool for each Power Platform task before acting - purpose-built plugin tools and MCP servers first, then the Dataverse SDK, Web API or pac CLI, and browser automation (Playwright) only for what has no API - and never tell the user something can't be done while browser automation could do it. Prevents the two failure modes: driving the maker portal through a browser for work an SDK does in one call (slow, brittle, costly), and refusing work that only the UI can do. Trigger whenever several tools could do the job: "use Playwright", "open the browser", "click through the portal", "is there an API for this", "bulk update records", "load this data", "create these columns", "change this setting", "check it looks right", "why is this so slow", "can you do this", and before saying any Power Platform task is impossible. Also trigger when browser automation is about to be used for data, schema, solution or flow work. When in doubt, trigger.
8스타 - writing-skillsPowercademy/powercademy-skills
This skill holds the Powercademy Skills house standard and the lint-enforced constraints that CI rejects violations of - dual-runtime portability rules, description limits, path conventions, the mechanics quarantine, redaction policy. Reviewing or authoring a marketplace skill without loading it will miss enforced constraints and fail CI. Trigger whenever the user says "write a skill", "new skill", "create a plugin", "add a skill to the marketplace", "review this SKILL.md", "review my skill", "improve this trigger description", "why isn't my skill triggering", or mentions a SKILL.md file, a trigger description, a skill description, authoring or reviewing an agent skill, or a skills marketplace in any way. Also trigger before authoring any SKILL.md, when editing a trigger description, or when promoting lessons from a private checklist into public skills. If the task is creating, modifying, reviewing, or structuring agent skills or plugins, trigger. When in doubt, trigger.
8스타
conventions 플러그인 질문
conventions 플러그인은 어떻게 설치하나요?
Claude Code에서 /plugin marketplace add Powercademy/powercademy-skills를 실행한 다음 /plugin install conventions@powercademy-skills을 실행하십시오.
conventions 플러그인에는 무엇이 포함되나요?
conventions은(는) 6개 스킬을(를) 묶습니다.
conventions 플러그인을 어떻게 업데이트하거나 삭제하나요?
shell에서 claude plugin update conventions@powercademy-skills를 사용하여 업데이트하거나 /plugin의 Installed 탭에서 수행하세요. 삭제하려면 /plugin uninstall conventions@powercademy-skills을 사용하세요.
conventions 플러그인의 라이선스는 무엇인가요?
플러그인 manifest에 명시된 대로 MIT입니다.