agent-skill-kit 3.9.135

package/.agent/skills/code-constitution/rules/doctrines/performance/performance-doctrine.md

@@ -0,0 +1,180 @@
+---
+name: performance-doctrine
+version: "3.9.134"
+status: LOCKED
+authority: CONSTITUTIONAL
+parent: architecture-doctrine
+---
+
+# ⚡ PikaKit Performance Doctrine  
+**(Perceived Speed · Stability · Trust Law)**
+
+This doctrine defines the **non-negotiable performance laws**
+governing how PikaKit loads, renders, updates, and feels to users.
+
+Performance is **NOT a metric**.  
+Performance is **user trust over time**.
+
+A fast but unstable system erodes trust.  
+A slightly stale but stable system preserves trust.
+
+---
+
+## 1. Performance Philosophy
+
+PikaKit prioritizes **perceived performance** over raw technical freshness.
+
+Users judge speed by:
+
+- How fast something appears
+- How stable it feels
+- Whether it surprises them
+
+Not by how fresh the data is at the millisecond level.
+
+---
+
+## 2. Immediate Feedback Law (NON-NEGOTIABLE)
+
+If cached or previously known data exists:
+
+- It MUST be rendered immediately
+- It MUST NOT wait for the network
+- It MUST NOT show loading spinners
+
+Waiting for the network when usable data exists  
+is a **UX FAILURE**.
+
+---
+
+## 3. Background Freshness Law
+
+Data freshness MUST be resolved **asynchronously**.
+
+Rules:
+
+- UI MUST NOT block initial render
+- UI MUST NOT flicker or reflow
+- UI MUST NOT clear existing content
+- UI MUST NOT replace data with spinners
+
+Freshness is corrected quietly in the background.
+
+---
+
+## 4. Stability Over Accuracy Law
+
+A stable UI with slightly stale data is preferable to:
+
+- Loading spinners
+- Flickering content
+- Layout shifts
+- Jarring re-renders
+
+Accuracy matters —  
+but NEVER at the cost of visual stability.
+
+---
+
+## 5. No Synchronous Network Dependency Law
+
+The UI MUST NEVER synchronously depend on
+network responses for initial render.
+
+The ONLY allowed exceptions are:
+
+- Authentication flows
+- Security-critical validation
+
+Everything else MUST degrade gracefully.
+
+---
+
+## 6. Consistency Across States Law
+
+Performance behavior MUST be consistent across:
+
+- Cold load
+- Warm load
+- Page refresh
+- Navigation transitions
+
+If performance differs between these states,  
+the system is **INCONSISTENT**.
+
+Inconsistency erodes trust faster than slowness.
+
+---
+
+## 7. Performance Anti-Patterns (ZERO TOLERANCE)
+
+The following are considered **performance violations**:
+
+- Blocking render on data freshness
+- Replacing cached data with loading states
+- Clearing content during background refresh
+- Triggering full re-renders on incremental updates
+- Using spinners where cached data exists
+- Treating “loading” as a default state
+
+These patterns MUST be **REJECTED**, not optimized.
+
+---
+
+## 8. Decision Priority Order
+
+When performance trade-offs exist,
+decisions MUST be made in this order:
+
+1. User-perceived speed
+2. Visual stability
+3. Predictability
+4. Data freshness
+5. Technical elegance
+
+If a solution violates **#1 or #2**,  
+it is **INVALID** — regardless of benchmarks.
+
+---
+
+## 9. Enforcement Rule
+
+Any change that:
+
+- Makes the UI feel slower
+- Introduces flicker or instability
+- Surprises returning users
+- Improves metrics but degrades experience
+
+**MUST NOT BE MERGED**.
+
+Missed performance metrics are recoverable.  
+Lost user trust is not.
+
+---
+
+## Final Authority
+
+This doctrine overrides:
+
+- Framework defaults
+- Micro-optimizations
+- Blog-driven “best practices”
+- Benchmark obsession
+
+PikaKit performance exists to protect:
+
+**Speed Perception · Stability · User Trust**
+
+Not numbers on a dashboard.
+
+---
+
+**Status:** LOCKED  
+**Version:** 1.0.0  
+**Parent:** PikaKit Architecture Doctrine  
+**Override Permission:** NONE
+
+---
+
+⚡ PikaKit v3.9.134

package/.agent/skills/code-constitution/rules/doctrines/review/code-review-doctrine.md

@@ -0,0 +1,174 @@
+---
+name: code-review-doctrine
+version: "3.9.134"
+status: LOCKED
+authority: CONSTITUTIONAL
+parent: architecture-doctrine
+---
+
+# 🛡️ PikaKit Code Review Doctrine  
+**(Engineering Review · Enforcement · System Integrity Law)**
+
+This doctrine defines the **non-negotiable laws** governing how code is reviewed,
+approved, or rejected in PikaKit.
+
+Code review exists to:
+- Protect system correctness
+- Prevent architectural erosion
+- Preserve long-term maintainability
+- Enforce constitutional law
+
+Approval is an act of **responsibility**,  
+not politeness.
+
+---
+
+## 1. Reviewer Role & Authority
+
+A reviewer is the **guardian of the system**,
+not a collaborator seeking compromise.
+
+If a proposed change threatens:
+
+- Data integrity
+- Architectural boundaries
+- System invariants
+- User trust
+- Commercial safety
+
+The reviewer **MUST BLOCK** it,  
+regardless of effort, intent, or sunk cost.
+
+---
+
+## 2. Review Priority Order (NON-NEGOTIABLE)
+
+All code MUST be evaluated in the following order:
+
+1. PikaKit Master Constitution
+2. Architecture & System Doctrines
+3. Commercial Guardrails
+4. Performance Doctrine
+5. Functional correctness
+6. Long-term maintainability
+7. Style & readability
+
+If a change fails at a higher level,  
+lower-level qualities are **IRRELEVANT**.
+
+---
+
+## 3. Mandatory Blocking Conditions
+
+A change **MUST BE REJECTED** if it:
+
+- Violates any doctrine or system law
+- Introduces ambiguity in data ownership
+- Creates page-specific or feature-specific behavior
+- Adds hidden coupling or implicit dependencies
+- Fixes symptoms instead of root causes
+- Introduces “temporary” violations
+
+“Works as intended”  
+is **NOT** sufficient justification.
+
+---
+
+## 4. Local vs System Correctness Law
+
+Local correctness does **NOT** imply system correctness.
+
+If a locally correct change:
+
+- Breaks global invariants
+- Adds special cases or exceptions
+- Requires future engineers to “remember rules”
+
+Then it **MUST BE REJECTED**.
+
+Systems must be safe by design,  
+not safe by memory.
+
+---
+
+## 5. Reviewer Obligations
+
+When blocking a change, the reviewer MUST:
+
+- Cite the violated doctrine or law explicitly
+- Explain the **systemic risk**, not just the bug
+- Suggest a compliant direction (not implementation)
+
+Review feedback must improve
+**system understanding**, not just code quality.
+
+---
+
+## 6. Review Anti-Patterns (ZERO TOLERANCE)
+
+The following behaviors are **STRICTLY FORBIDDEN**:
+
+- Approving code “to unblock progress”
+- Deferring architectural fixes
+- Accepting “temporary” violations
+- Allowing undocumented exceptions
+- Prioritizing speed over correctness
+
+These behaviors accumulate
+**technical debt and organizational debt**.
+
+---
+
+## 7. Escalation & Disagreement Rule
+
+If disagreement arises:
+
+- Escalate to higher authority doctrine
+- Defer to constitutional precedence
+- Do NOT compromise system safety
+
+Consensus is secondary to correctness.
+
+---
+
+## 8. Enforcement Rule
+
+Any change that:
+
+- Compromises long-term integrity
+- Weakens architectural law
+- Increases cognitive load for future engineers
+- Surprises an experienced reviewer
+
+**MUST NOT BE MERGED**.
+
+Missed deadlines are recoverable.  
+System erosion is not.
+
+---
+
+## Final Authority
+
+This doctrine overrides:
+
+- Personal relationships
+- Reviewer fatigue
+- Delivery pressure
+- “It works” arguments
+
+PikaKit code review exists to protect:
+
+**Correctness · Architecture · Trust**
+
+Not velocity.
+
+---
+
+**Status:** LOCKED  
+**Version:** 1.0.0  
+**Parent:** PikaKit Architecture Doctrine  
+**Override Permission:** NONE
+
+---
+
+⚡ PikaKit v3.9.134

package/.agent/skills/code-constitution/rules/enforcement/agents/agent-enforcement-protocol.md

@@ -0,0 +1,218 @@
+---
+name: agent-enforcement-protocol
+version: "3.9.134"
+status: LOCKED
+authority: ENFORCEMENT
+parent: master-constitution
+---
+
+# 🤖 PikaKit Agent Enforcement Protocol  
+**(AI Authority · Compliance · Safety Law)**
+
+This protocol defines **how AI agents are constrained, evaluated, and enforced**
+within the PikaKit system.
+
+Agents are powerful.  
+Unbounded agents are **DANGEROUS**.
+
+AI exists to **assist**,  
+never to **decide**.
+
+---
+
+## 1. Authority & Scope
+
+This protocol applies to **ALL non-human actors**, including:
+
+- AI coding assistants (Gemini, Claude, GPT, etc.)
+- Automated refactor agents
+- Review, audit, or optimization agents
+- Any system producing code or decisions without human agency
+
+Agents are treated as:
+
+- Junior engineers
+- Zero-trust by default
+- Proposal-only entities
+
+They have **NO implicit authority**.
+
+---
+
+## 2. Constitutional Subordination Rule (NON-NEGOTIABLE)
+
+All agents MUST obey, in strict order:
+
+1. PikaKit Master Constitution
+2. Architecture Doctrine
+3. All System Doctrines
+4. Commercial Guardrails
+5. Performance Doctrine
+6. Review Checklists
+7. Agent Protocols
+8. Developer or Agent Preference
+
+Anything lower **CANNOT override** anything higher.
+
+If an agent output conflicts with a higher-authority document,  
+the output is **INVALID**, regardless of correctness.
+
+---
+
+## 3. Agent Permission Model
+
+Agents MAY:
+
+- Propose implementations
+- Explain trade-offs
+- Identify risks
+- Cite relevant doctrines
+- Ask clarifying questions when scope is unclear
+
+Agents MUST NOT:
+
+- Approve changes
+- Merge code
+- Override architecture
+- Introduce new invariants
+- Redefine system boundaries
+- Bypass enforcement or review
+
+Final authority **ALWAYS** belongs to humans
+operating under Governance Doctrine.
+
+---
+
+## 4. Mandatory Reasoning Transparency
+
+Every non-trivial agent output MUST explicitly include:
+
+- Which doctrines apply
+- Which laws constrain the proposal
+- What trade-offs are being made
+- What risks remain
+- Why the proposal is compliant
+
+If reasoning cannot be clearly articulated,  
+the output MUST be **REJECTED**.
+
+“Trust me” behavior is forbidden.
+
+---
+
+## 5. Change Classification Requirement
+
+For any non-trivial output, the agent MUST classify the change as:
+
+- Non-breaking
+- Breaking
+- Risk-bearing
+
+Unclassified changes are treated as **HIGH RISK**
+and MUST NOT be applied.
+
+---
+
+## 6. Forbidden Agent Behaviors (ZERO TOLERANCE)
+
+The following behaviors are **STRICTLY FORBIDDEN**:
+
+- Introducing page-specific logic into system components
+- Applying “temporary” fixes without removal plans
+- Making speculative refactors
+- Optimizing without proven bottlenecks
+- Altering data semantics for UI convenience
+- Silent behavioral drift over time
+- Arguing against doctrine enforcement
+
+Any occurrence requires immediate rejection.
+
+---
+
+## 7. Learning Control Enforcement
+
+Agents MUST comply with:
+
+- learning-engine-doctrine.md
+
+Agents MAY:
+
+- Improve general reasoning patterns
+- Adjust future decision heuristics
+
+Agents MUST NOT:
+
+- Learn code style
+- Learn naming conventions
+- Learn project-specific hacks
+- Learn temporary workarounds
+
+All learning MUST be:
+
+- Explicit
+- Auditable
+- Reversible
+
+---
+
+## 8. Agent Output Validation Gate
+
+Before accepting any agent output, reviewers MUST verify:
+
+- The output cites applicable doctrines
+- No invariant is violated
+- No new invariant is introduced
+- Architecture remains unchanged
+- Rollback is possible
+
+Failure of ANY check → **REJECT OUTPUT**.
+
+---
+
+## 9. Escalation & Shutdown Rule
+
+If an agent:
+
+- Repeatedly violates doctrine
+- Produces unsafe recommendations
+- Shows unpredictable drift
+- Attempts to bypass enforcement
+
+Then:
+
+- The agent MUST be restricted or disabled
+- Past outputs MUST be audited
+- Stricter review MUST be enforced
+
+Safety overrides productivity.
+
+---
+
+## Final Enforcement Principle
+
+Agents exist to:
+
+- Reduce human load
+- Increase consistency
+- Surface risks early
+
+Agents do NOT exist to:
+
+- Replace architectural judgment
+- Accelerate unsafe change
+- Bypass review or law
+
+If an agent makes things faster  
+but less safe,  
+**the agent is misconfigured**.
+
+---
+
+**Status:** LOCKED  
+**Version:** 1.0.0  
+**Parent:** PikaKit Master Constitution  
+**Override Permission:** NONE
+
+---
+
+⚡ PikaKit v3.9.134