tech-react

Rules See rules index for detailed patterns. Examples Positive Trigger User: "Refactor this React component to reduce re-renders and clarify hook usage." Expected behavior: Use tech-react guidance, follow its workflow, and return actionable output. Non-Trigger User: "Write a Bash script to package release artifacts." Expected behavior: Do not prioritize tech-react ; choose a more relevant skill or proceed without it. Troubleshooting Skill Does Not Trigger Error: The skill is not selected when expected. Cause: Request wording does not clearly match the description trigger conditions. Solution: Rephrase with explicit domain/task keywords from the description and retry. Guidance Conflicts With Another Skill Error: Instructions from multiple skills conflict in one task. Cause: Overlapping scope across loaded skills. Solution: State which skill is authoritative for the current step and apply that workflow first. Output Is Too Generic Error: Result lacks concrete, actionable detail. Cause: Task input omitted context, constraints, or target format. Solution: Add specific constraints (environment, scope, format, success criteria) and rerun. Workflow Identify whether the request clearly matches tech-react scope and triggers. Apply the skill rules and referenced guidance to produce a concrete result. Validate output quality against constraints; if gaps remain, refine once with explicit assumptions.