Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Purpose: Deep, honest, no-holds-barred system health analysis for the Pomo-Flow Vue.js application that tells the complete truth about system status, performance, and integrity.
Philosophy
This skill provides brutally honest system analysis with:
Zero sugar-coating - Tells you exactly what's wrong
Complete coverage - Analyzes every system layer
Evidence-based findings - Provides proof for all issues
Prioritized fixes - Shows what matters most
Performance impact - Quantifies how issues affect users
Analysis Layers
🔧 Core Application Health
Vue.js application initialization and lifecycle
Component tree integrity and performance
Router configuration and navigation health
State management (Pinia) integrity
Bundle analysis and loading performance
📊 Performance Metrics
First Contentful Paint (FCP) and Largest Contentful Paint (LCP)
Time to Interactive (TTI) and Cumulative Layout Shift (CLS)
"TaskCard.vue has a render time of 127ms (should be <16ms), causing 40% of users to experience jank. This component renders 1,247 times per page load and uses 8.7MB of memory. Fix this by implementing virtual scrolling."
Instead of saying:
"Consider updating dependencies"
The skill says:
"You have 12 critical security vulnerabilities, including CVE-2024-12345 in package 'example-lib' v1.2.3. Attackers can exploit this to execute remote code. Update to v1.2.4 immediately."
Success Criteria
The analysis is successful when it:
Tells the complete truth about system health
Provides actionable evidence for every finding
Prioritizes issues by user impact
Quantifies performance impact with real metrics
Delivers immediate value with clear next steps
This skill exists to ensure you never have false confidence about your application's health. It provides the brutal honesty needed to build truly excellent software.
Created for Pomo-Flow Vue.js projectComprehensive, honest, no-compromise system analysis
MANDATORY USER VERIFICATION REQUIREMENT
Policy: No Fix Claims Without User Confirmation
CRITICAL: Before claiming ANY issue, bug, or problem is "fixed", "resolved", "working", or "complete", the following verification protocol is MANDATORY:
Step 1: Technical Verification
Run all relevant tests (build, type-check, unit tests)
Verify no console errors
Take screenshots/evidence of the fix
Step 2: User Verification Request
REQUIRED: Use the AskUserQuestion tool to explicitly ask the user to verify the fix:
"I've implemented [description of fix]. Before I mark this as complete, please verify:
1. [Specific thing to check #1]
2. [Specific thing to check #2]
3. Does this fix the issue you were experiencing?
Please confirm the fix works as expected, or let me know what's still not working."
Step 3: Wait for User Confirmation
DO NOT proceed with claims of success until user responds
DO NOT mark tasks as "completed" without user confirmation
DO NOT use phrases like "fixed", "resolved", "working" without user verification
Step 4: Handle User Feedback
If user confirms: Document the fix and mark as complete
If user reports issues: Continue debugging, repeat verification cycle
Prohibited Actions (Without User Verification)
Claiming a bug is "fixed"
Stating functionality is "working"
Marking issues as "resolved"
Declaring features as "complete"
Any success claims about fixes
Required Evidence Before User Verification Request
Technical tests passing
Visual confirmation via Playwright/screenshots
Specific test scenarios executed
Clear description of what was changed
Remember: The user is the final authority on whether something is fixed. No exceptions.
