Menu
SkillsMP a collecté 19 skills depuis tilework-tech/nori-luma-cli. Ouvrez un skill pour examiner sa source et ses détails.
Affichage de 19 skills collectés sur 19.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Langue du texte source : anglais
IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Langue du texte source : anglais
Read this skill whenever you need to build a cli where the primary consumer is the agent.
Langue du texte source : anglais
Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration
Langue du texte source : anglais
Use when asked to create a new skillset.
Langue du texte source : anglais
Use this skill when faced with a difficult debugging task where you need to replicate some bug or behavior in order to see what is going wrong.
Langue du texte source : anglais
Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts
Langue du texte source : anglais
Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
Langue du texte source : anglais
Use this skill to split large plans into smaller chunks. This skill manages your context window for large tasks. Use it when a task will take a long time and cause context issues.
Langue du texte source : anglais
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Langue du texte source : anglais
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
Langue du texte source : anglais
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Langue du texte source : anglais
Use when experimenting with different user interfaces or user experiences.
Langue du texte source : anglais
Use this when you have finished making code changes and you are ready to update the documentation based on those changes.
Langue du texte source : anglais
Use this whenever you need to create an isolated workspace.
Langue du texte source : anglais
Describes how to use abilities. Read before any conversation.
Langue du texte source : anglais
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal…
Langue du texte source : anglais
Use after TDD is finished, to review and clean the testing additions
Langue du texte source : anglais
Use this skill to build features or debug anything that uses a webapp frontend.
Langue du texte source : anglais