siso-internal
Complete guide to SISO Internal task management and operations system with Claude Code
Découvrez les skills devops project management, comparez leurs dépôts et consultez leurs instructions.
Complete guide to SISO Internal task management and operations system with Claude Code
Send lightweight status updates to a human during long-running agent work
Turn messy qualitative feedback into a prioritized, actionable backlog
Skill for optimizing content, microcopy, and CTA placement for mobile viewports.
Skill for ensuring visual consistency and preventing layout shifts during responsive transitions.
[70] CLOSE. Manage task lifecycle with correct statuses and no duplicates. Ensure each task has one status, artifacts match claims, and no task appears in multiple places. Use when managing task lists, updating...
[21] UNDERSTAND. Deep research workflow for this project using 150% scope (100% core + 50% boundary), evidence-based reasoning, and structured investigation notes. Use when the task requires investigation, root...
[62] VALIDATE. Final self-check before delivery. Verify goal alignment, completeness, correctness, and identify residual risks. Produces quality score (0-100) and delivery status. Use when completing any signif...
[40] PLAN. Create clear action plans with steps, success criteria, and risk awareness. Use before implementing features, making changes, starting projects, or anytime you need a roadmap to success. Triggers on...
[01] META. Сканирует доступные skills, создает план выполнения и идет шаг за шагом с подтверждением каждого этапа. Triggers on complex tasks, multi-step work, or when structured execution is needed.
[74] CLOSE. Quick checkpoint during active work when context is running low. Use multiple times per development cycle to preserve progress and lessons. Lighter than close-session — no full handoff needed. Trigg...
[02] META. Create new skills when existing ones don't cover the task. Analyze unique requirements, build framework (Frame → Research → Plan → Execute), integrate risks, and declare new skill. Use when facing no...
[71] CLOSE. Quick, safe cleanup after completing a milestone. Fix objective issues only (syntax errors, dead code, poor naming). Must be
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas fil...
Generate comprehensive execution plans for features, epics, or large tasks. Use when asked to plan a feature, create a roadmap, break down work into tracks/beads, or design implementation strategy.
Research and understand React projects and features. Use when asked to explore a React codebase, check if a feature exists, understand component relationships, or map project structure. Specialized for React/Vi...
Systematically debug and fix bugs through triage, reproduction, root cause analysis, and verified fixes. Use when asked to fix a bug, debug an issue, investigate a problem, or resolve an error.
Explores and maps Zalo Mini App codebases. Use when asked to understand project structure, find features, audit zmp-sdk/zmp-ui usage, or analyze a ZMP codebase.
Checklist for finishing work, pushing a branch, and opening a ready-for-review PR with tests and tracker updates. Use when asked to "land the plane"
Naming conventions for planning documents in prompts/. Use when creating plans, PRDs, research reports, idea capture or other workflow documents. Triggers on (1) creating new planning documents, (2) naming PRDs...
Interview user in-depth about what they're building, then write a comprehensive spec. Use when the user wants to plan a feature, design a system, or needs help defining requirements.
Creates atomic git commits following Conventional Commits specification with detailed, well-structured messages. Analyzes changes and splits them into logical units. Use when committing code changes that need p...
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD, write requirements, or spec out a feature.
Create Product Requirement Documents through structured interview. Use when user says "create a PRD", "write a PRD for X", "document requirements for X", "start a PRD".
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.