メニュー
กำหนด coding convention per project — naming, folder structure, linting, formatting — ให้ทีม Dev ทำงานบน standard เดียวกัน
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | Coding Standards |
| description | กำหนด coding convention per project — naming, folder structure, linting, formatting — ให้ทีม Dev ทำงานบน standard เดียวกัน |
Purpose: สร้าง Coding Standards Document ให้แต่ละ project Dev ทุกคนใช้ convention เดียวกัน ลด conflict, ลด review time
สร้างไฟล์ {ProjectFolder}/Scaffold/CODING-STANDARDS.md:
| Item | Convention | Example |
|---|---|---|
| Files | kebab-case | user-service.ts, order-model.py |
| Classes | PascalCase | UserService, OrderModel |
| Functions | camelCase (JS/TS) / snake_case (Python/Go) | getUser(), get_user() |
| Constants | UPPER_SNAKE | MAX_RETRY, API_BASE_URL |
| DB Tables | snake_case plural | users, order_items |
| DB Columns | snake_case | created_at, user_id |
| API Endpoints | kebab-case plural | /api/v1/order-items |
| Components | PascalCase | UserProfile.tsx, OrderList.vue |
| Pattern | When to Use |
|---|---|
| Feature-based | Project > 10 modules, ทีม > 3 คน |
| Layer-based | Project < 10 modules, ทีม <= 3 คน |
| Domain-driven | Complex business logic, multiple bounded contexts |
| Rule | Standard |
|---|---|
| Indentation | 2 spaces (JS/TS) / 4 spaces (Python) |
| Max line length | 100 characters |
| Imports | Group by: stdlib → third-party → local, alphabetical within group |
| Comments | Thai OK for business logic, English for technical |
| Error handling | Always catch + log + meaningful message, never swallow errors |
| API Response | Consistent format: { success, data, error, meta } |
| Item | Format |
|---|---|
| Branch | {type}/{project-code}/{short-desc} e.g. feat/P07/login-flow |
| Commit | {type}({project}): {description} e.g. feat(P07): add login API |
| PR Title | [{project}] {type}: {description} |
Commit types: feat, fix, refactor, test, docs, chore, style
| Item | Standard |
|---|---|
| Minimum coverage | 80% |
| Test naming | should {action} when {condition} |
| Test structure | Arrange → Act → Assert |
| Required tests | Happy path + Error cases + Edge cases per module |
Auto-load ตาม tech stack ที่ user ระบุ:
| Language | Key Rules |
|---|---|
| TypeScript | ห้าม any, explicit return types, async/await, strict null checks, named exports |
| Python | Type hints required, Google docstrings, specific exceptions, f-strings, pathlib, dataclasses |
| Go | Explicit error handling, context propagation, interface-first, struct composition |
| Rust | Ownership patterns, minimize unsafe, Result/Option over panic |
| Java | Optional over null, immutable default, Stream API, proper exception hierarchy |
| Swift | Protocol-oriented, value types, async/await concurrency, optional handling |
สำหรับ AI product projects: tenant isolation, cost tracking, provider abstraction, prompt safety, rate limiting, fallback chains, output validation
Auto-include ทุก project: input validation (whitelist), output encoding (XSS prevention), no secrets in code, auth on every operation, OWASP Top 10
pmo-code-scaffold อ่าน CODING-STANDARDS.md เพื่อ generate code ตาม conventionpmo-dev-report เทียบ code กับ CODING-STANDARDS.mdpmo-ci-cd-template generate linter config ตาม standardspmo-security-scan ใช้ security standards เป็น baselinePre/Post execution validation + Phase Gate enforcement — ป้องกันการข้าม step, auto-validate output, ให้คะแนน quality score
สแกน code ใน Scaffold/ ด้วย 53 security rules (6 หมวด) — secrets, permissions, injection, AI-specific, config, dependencies — ก่อน deploy หรือหลัง Dev report
Coordinate PM/Dev/QA agents แบบ Pipeline Pattern — auto-route งานตาม role, ส่งต่ออัตโนมัติเมื่อ status เปลี่ยน, track progress ทุก handoff
Create color-coded teaching scripts / presenter talking-point documents (.md) that serve as a "live reading book" for speakers. The output is a markdown file where each color tells the presenter what to do: blue = speak this line, red = pronunciation guide, dark blue = slide header, black = stage direction & audience engagement, yellow box = terminology. Use this skill whenever the user mentions: teaching script, talking points, presenter script, key talking point, speaker notes, lecture script, training script, presentation script, สคริปต์การสอน, สคริปต์วิทยากร, คำพูดที่ต้องอ่าน, หนังสือสำหรับพูด, or any request to create a document that guides a speaker through a slide deck with exact words to say, pronunciation help, and stage directions. Also trigger when the user uploads a PowerPoint (.pptx) and asks to write a script, narration, or talking points for it.
Use for QA evidence, release readiness, rollback review, and close-out decisions.
Use for build completion evidence, code review readiness, and ready-for-QA checks.