القائمة
Internal Structure-Behavior Design skill for conceptual modeling and structure design. Use only as part of the Structure-Behavior Design workflow.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Author or update tool-neutral knowledge packs in ai-knowledge-base.
A workflow for authoring Go tests. Starting from the table-driven test scaffold generated by gotests, it runs the cycle of test design -> adding test cases -> running -> fixing defects. Use when: (1) invoked via /go-test-authoring, (2) asked to "write tests" or "add tests" for Go, (3) asked to implement tests for a Go function or method.
Git commit with Conventional Commits format. Use when user asks to commit changes, says "commit", "/commit", or after completing code changes when explicitly asked to commit.
Create GitHub Pull Request with project's PR template. Use when user asks to create PR, says "create PR", "/pr-create", or after completing implementation when asked to open a pull request.
Address PR review feedback. Collect both unresolved inline comments and review-body comments on a GitHub PR, build a fix plan and turn it into tasks, then work through them one by one (assess -> fix -> commit -> push -> reply). Use when invoked as /pr-review-fix, when asked to "address the review comments" or "respond to PR feedback", or for follow-up work after a PR review.
Internal Structure-Behavior Design skill for interface, signature, and contract design. Use only as part of the Structure-Behavior Design workflow.
| id | structure-behavior-design.skill.conceptual-modeling |
| kind | skill |
| name | structure-behavior-design-conceptual-modeling |
| description | Internal Structure-Behavior Design skill for conceptual modeling and structure design. Use only as part of the Structure-Behavior Design workflow. |
| tags | ["structure-behavior-design","internal"] |
| tools | {"claude":{"enabled":true,"frontmatter":{"user-invocable":false}}} |
Model the problem area before designing packages, interfaces, or implementation.
Modeling is not limited to business domains.
Problem areas may include:
| Concept | Meaning | State | Behavior | Constraint / Invariant |
|---|
| Concept A | Relationship | Concept B | Notes |
|---|
