RohiRIK

USE WHEN separating trusted instructions from untrusted content or tool output.

USE WHEN hardening command execution, path handling, or installer boundaries.

USE WHEN handling credentials, env vars, logs, tests, or docs safely.

Reference for LTM memory commands, context hooks, and DB schema; use when the user mentions learning, recalling, forgetting, relating, or capturing memory, or when a session starts or the project changes.

Mines LTM memories from past git commits. Use when onboarding a repo into LTM, backfilling history after enabling gitLearn, or harvesting patterns after a sprint.

Reference for retrieved patterns and lessons from past sessions; use when prior fixes, gotchas, decisions, or earlier sessions may apply, or when asked what we learned before.

The LTM memory-tool contract — names, ritual, categories, phase map. USE WHEN recalling, learning, relating, or restoring memory.

Start, stop, or check the LTM graph visualization server; use when the user asks to open, launch, stop, kill, or check graph-server status.

Enforce universal coding standards and best practices.

Standards, patterns, and workflows for modern frontend development (React, Next.js, Performance). USE WHEN designing components, optimizing UI, or implementing state management.

Optimize job applications by tailoring resumes to job postings, generating customized cover letters, and preparing role-specific interview questions. Analyzes job descriptions to highlight relevant skills and experience. Use when users need to apply for jobs, customize resumes, or prepare for interviews.

Resume structure, achievement bullet formulas, ATS optimization, and job-targeted tailoring for software engineers. Use when reviewing resumes, crafting achievement bullets, extracting keywords from job descriptions, or tailoring content for specific roles.

This skill should be used when the user asks to "create a new dev-team agent", "scaffold a subagent", "port a Gemini/Cursor/Cline agent", "canonicalize an agent", or "validate the agents folder". Owns the full lifecycle — generate, research, validate, and update dev-team subagents to match the plugin's 7-section spec, tool allowlist, and task-tracker integration.