tilework-tech/nori-luma-cli

systematic-debugging

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

원문 언어: 영어

brainstorming

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

원문 언어: 영어

building-agentic-cli-tools

Read this skill whenever you need to build a cli where the primary consumer is the agent.

원문 언어: 영어

building-ui-ux

Use when implementing user interfaces or user experiences - guides through exploration of design variations, frontend setup, iteration, and proper integration

원문 언어: 영어

creating-a-skillset

Use when asked to create a new skillset.

원문 언어: 영어

creating-debug-tests-and-iterating

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.

원문 언어: 영어

creating-skills

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

원문 언어: 영어

finishing-a-development-branch

Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.

원문 언어: 영어

handle-large-tasks

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.

원문 언어: 영어

receiving-code-review

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

원문 언어: 영어

root-cause-tracing

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

원문 언어: 영어

test-driven-development

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

원문 언어: 영어

ui-ux-experimentation

Use when experimenting with different user interfaces or user experiences.

원문 언어: 영어

updating-noridocs

Use this when you have finished making code changes and you are ready to update the documentation based on those changes.

원문 언어: 영어

using-git-worktrees

Use this whenever you need to create an isolated workspace.

원문 언어: 영어

using-skills

Describes how to use abilities. Read before any conversation.

원문 언어: 영어

writing-plans

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…

원문 언어: 영어

test-scenario-hygiene

Use after TDD is finished, to review and clean the testing additions

원문 언어: 영어

webapp-testing

Use this skill to build features or debug anything that uses a webapp frontend.

원문 언어: 영어