phaselock

Category: Development & Coding | Uploader: infinri | Downloads: 0 | Version: v1.0（Latest）

Provides institutional coding knowledge ("Coding Bible") covering architectural decisions, coding standards, framework-specific rules, security expectations, performance guidelines, and approved patterns for AI-assisted development. Guides code generation, refactoring, architecture decisions, database query authoring, error handling, testing, and performance optimization. Activates on tasks involving code review, design decisions, SQL queries, PHP development, security review, or when project conventions and domain-specific rules must be consulted before proposing solutions.

Changelog: Source: GitHub https://github.com/infinri/Phaselock

Directory Structure

Current level: Root

📁 .claude/
- 📁 agents/
  - 📄 plan-guardian.md 2.9 KB
  - 📄 slice-builder.md 2.5 KB
  - 📄 static-analysis.md 1.0 KB
- 📁 hooks/
  - 📄 check-gate-approval.sh 2.4 KB
  - 📄 enforce-final-gate.sh 2.1 KB
  - 📄 pre-validate-file.sh 4.1 KB
  - 📄 validate-file.sh 5.7 KB
- 📄 CLAUDE.md 5.7 KB
📁 .idea/
- 📄 .gitignore 228 B
- 📄 ai-workflow.iml 281 B
- 📄 copilot.data.migration.agent.xml 190 B
- 📄 modules.xml 274 B
- 📄 php.xml 692 B
📁 bible/
- 📁 architecture/
  - 📄 principles.md 5.1 KB
- 📁 database/
  - 📄 sql-authoring.md 2.8 KB
- 📁 frameworks/
  - 📁 magento/
    
    📄 implementation-constraints.md 7.7 KB
    
    📄 runtime-constraints.md 12.2 KB
  - 📄 .gitkeep 0 B
- 📁 languages/
  - 📁 php/
    
    📄 coding-standards.md 1.4 KB
    
    📄 error-handling.md 1.5 KB
- 📁 performance/
  - 📄 profiling.md 4.1 KB
- 📁 playbooks/
  - 📄 .gitkeep 0 B
  - 📄 api-endpoint.md 1.2 KB
  - 📄 queue-feature.md 1.4 KB
- 📁 security/
  - 📄 .gitkeep 0 B
  - 📄 boundaries.md 1.6 KB
- 📁 testing/
  - 📄 unit-testing.md 1.8 KB
📁 enforcement/
- 📄 ai-checklist.md 4.2 KB
- 📄 operational-claims.md 5.8 KB
- 📄 reasoning-discipline.md 43.7 KB
- 📄 security-boundaries.md 6.3 KB
- 📄 system-dynamics.md 14.8 KB
📁 prompts/
- 📄 cascade-best-practices.md 1.5 KB
📁 rules/
- 📄 CORE_PRINCIPLES.md 1.2 KB
📄 .gitignore 7 B
📄 CONTRIBUTING.md 3.3 KB
📄 MANIFEST.md 3.9 KB
📄 OVERVIEW.md 5.1 KB
📄 README.md 10.2 KB
📄 SKILL.md 7.7 KB

SKILL.md

---
name: phaselock
description: >
  Provides institutional coding knowledge ("Coding Bible") covering architectural
  decisions, coding standards, framework-specific rules, security expectations,
  performance guidelines, and approved patterns for AI-assisted development.
  Guides code generation, refactoring, architecture decisions, database query
  authoring, error handling, testing, and performance optimization. Activates on
  tasks involving code review, design decisions, SQL queries, PHP development,
  security review, or when project conventions and domain-specific rules must be
  consulted before proposing solutions.
metadata:
  author: lucio-saldivar
  version: "1.0"
---

# Phaselock — Coding Bible

## Workflow

1. **Identify the task domain** from the navigation table below
2. **Read only the relevant documents** — do not load the entire knowledge base
3. **State which documents were consulted** before proposing any solution
4. **If the task involves plugins, observers, validation, or entity retrieval**: follow the **Phased Implementation Protocol** (`ENF-GATE-001`–`007` in [enforcement/reasoning-discipline.md](enforcement/reasoning-discipline.md)):
   - **Phase A** → Call-path declaration ONLY → halt for review
   - **Phase B** → Domain invariant declaration ONLY → halt for review
   - **Phase C** → Seam justification ONLY → halt for review
   - **Phase D** → Failure & concurrency modeling ONLY (when triggered) → halt for review
   - **Test Skeletons** → Generate test skeletons with assertions BEFORE implementation → halt for review (`ENF-GATE-007`)
   - **Sliced Code Generation** → Generate implementation in dependency-ordered slices, each with self-validation and human gate (`ENF-GATE-006`)
5. **If the task involves concurrency, async processing, state transitions, or multi-actor writes**: Phase D is mandatory. See trigger conditions in [enforcement/system-dynamics.md](enforcement/system-dynamics.md).
6. **Post-generation verification is mandatory**: structured findings table (`ENF-POST-006`), static analysis (`ENF-POST-007`), and operational proof traces (`ENF-POST-008`) must be produced per slice.
7. **If guidance is missing or ambiguous**: state it explicitly, ask for clarification, propose a conservative default. Silent guessing is never allowed.

## Task → document navigation

Read the documents listed for each matching task type. Start with [rules/CORE_PRINCIPLES.md](rules/CORE_PRINCIPLES.md) for any code task.

### Architecture & design decisions

When introducing modules, changing system boundaries, or modifying core flows:

- [bible/architecture/principles.md](bible/architecture/principles.md) — Code organization, extension points, dependency injection, named constants, single source of truth for multi-channel data (`ARCH-ORG-001`, `ARCH-EXT-001`, `ARCH-DI-001`, `ARCH-CONST-001`, `ARCH-SSOT-001`)

### Database / SQL

When writing queries, diagnosing query performance, or handling transactions:

- [bible/database/sql-authoring.md](bible/database/sql-authoring.md) — Named binds, minimal string fragmentation, readable formatting (`DB-SQL-001`, `DB-SQL-002`, `DB-SQL-003`)

### PHP development

When writing PHP code, handling errors, or enforcing type safety:

- [bible/languages/php/coding-standards.md](bible/languages/php/coding-standards.md) — DocBlock types, try-catch standards (`PHP-TYPE-001`, `PHP-ERR-002`)
- [bible/languages/php/error-handling.md](bible/languages/php/error-handling.md) — Fail fast, graceful degradation (`PHP-ERR-001`, `PHP-ERR-002`)

### Performance & optimization

When optimizing slow paths, addressing resource issues, or introducing caching:

- [bible/performance/profiling.md](bible/performance/profiling.md) — Algorithm complexity, optimization order, lazy loading, query budget declaration (`PERF-BIGO-001`, `PERF-OPT-001`, `PERF-LAZY-001`, `PERF-QBUDGET-001`)

### Frameworks / Magento 2

When writing plugins, observers, validation, or entity retrieval in Magento 2:

- [bible/frameworks/magento/implementation-constraints.md](bible/frameworks/magento/implementation-constraints.md) — Persistence-backed validation, repository-only retrieval, quote state timing, plugin targeting, totals collector idempotency, CartTotalRepository stale-read behavior (`FW-M2-001`, `FW-M2-002`, `FW-M2-003`, `FW-M2-004`, `FW-M2-005`, `FW-M2-006`)
- [bible/frameworks/magento/runtime-constraints.md](bible/frameworks/magento/runtime-constraints.md) — MSI salability authority, order state machine, config patterns, endpoint authorization, queue infrastructure, multi-website stock (`FW-M2-RT-001`, `FW-M2-RT-002`, `FW-M2-RT-003`, `FW-M2-RT-004`, `FW-M2-RT-005`, `FW-M2-RT-006`)

### Testing

When adding tests, refactoring with risk, or addressing regressions:

- [bible/testing/unit-testing.md](bible/testing/unit-testing.md) — TDD, test isolation, integration testing (`TEST-TDD-001`, `TEST-ISO-001`, `TEST-INT-001`)

### System dynamics & concurrency

When building features with concurrent actors, message queues, state machines, async processing, or multi-website behavior:

- [enforcement/system-dynamics.md](enforcement/system-dynamics.md) — Concurrency simulation, temporal truth sources, state transition atomicity, policy vs mechanism separation, integration reality check (`ENF-SYS-001`, `ENF-SYS-002`, `ENF-SYS-003`, `ENF-SYS-004`, `ENF-SYS-005`)

### Security & access control

When exposing endpoints (REST, GraphQL, admin, storefront) or handling data access:

- [enforcement/security-boundaries.md](enforcement/security-boundaries.md) — Access boundary declarations, data exposure minimization (`ENF-SEC-001`, `ENF-SEC-002`)

### Operational claims & queue infrastructure

When making performance/throughput claims or configuring message queues:

- [enforcement/operational-claims.md](enforcement/operational-claims.md) — Operational claim validation, queue configuration completeness (`ENF-OPS-001`, `ENF-OPS-002`)

### AI behavior & code generation

When reviewing AI-generated code or understanding assistant behavior expectations:

- [enforcement/ai-checklist.md](enforcement/ai-checklist.md) — Pre-implementation checklist, minimal code generation rules
- [enforcement/reasoning-discipline.md](enforcement/reasoning-discipline.md) — Mandatory pre-implementation reasoning, phased code generation, test-first gate, post-generation verification (structured findings table, static analysis gate, operational proof traces), context retrieval discipline, Phase D hard gate, plan-to-code completeness verification (`ENF-PRE-001`–`004`, `ENF-GATE-001`–`007`, `ENF-GATE-FINAL`, `ENF-POST-001`–`008`, `ENF-CTX-001`–`003`)
- [enforcement/system-dynamics.md](enforcement/system-dynamics.md) — System dynamics enforcement, Phase D protocol (`ENF-SYS-001`–`006`)
- [enforcement/security-boundaries.md](enforcement/security-boundaries.md) — Security boundary enforcement (`ENF-SEC-001`–`002`)
- [enforcement/operational-claims.md](enforcement/operational-claims.md) — Operational claim enforcement (`ENF-OPS-001`–`002`)
- [prompts/cascade-best-practices.md](prompts/cascade-best-practices.md) — Prompt engineering guidelines

## Rule format

All enforceable rules use formal blocks with unique IDs wrapped in `<!-- RULE START/END -->` markers. See [CONTRIBUTING.md](CONTRIBUTING.md) for the full rule format specification.

## Additional references

- [README.md](README.md) — Human-readable project overview
- [MANIFEST.md](MANIFEST.md) — Extended task-to-document mapping
- [OVERVIEW.md](OVERVIEW.md) — Complete directory index with descriptions

## Authority model

This skill provides reference and reasoning material only. It does not grant file access, override global rules, or authorize actions. All rules originate from explicit human intent — the agent may format but never invent rules.

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

phaselock

Directory Structure

SKILL.md

Report

Notice