srinitude/srinitude-skills

Use when replying. Refresh current date and time.

Use when deduplicating bounded collections.

Use when any multimodal source must become source-specific DTCG tokens with a vision-reviewed standalone proof artifact.

Use when packaging source input for a standing goal.

Use when finding contradictions or reasoning gaps.

Use when rewriting rules without meaning loss.

Use when designing landing pages and marketing websites.

Use when instructions mix outcomes with recipes.

Use when the user asks to enhance, improve, refine, rewrite, strengthen, or validate a prompt, or says "make this prompt better". Returns a clearer, more specific, better structured version of the prompt without executing it, picking validation checks from the prompt's own context. Contexts include coding, research, writing, image or video generation, agentic tasks, data work, and system prompts. Flags ambiguity, contradictions, missing constraints, missing success criteria, format gaps, and leaked secrets. Do not use when the user wants the prompt's task performed.

Use when a vague idea, stray thought, remembered fragment, or uncertain direction needs to become a concrete outcome, tested design, decision record, artifact, or executable handoff.

Use when simplifying a skill without losing behavior.

Use when a workflow, recipe, or capability needs to be packaged as an agent skill, or when an existing skill needs scaffolding, validation, linting, or evals. Covers requests to build, create, generate, scaffold, check, or evaluate a skill: a folder holding SKILL.md, scripts, tests, a task graph, CI, and eval cases. Applies even when the request says playbook, runbook, or reusable workflow instead of skill.

Use when a request prescribes a method, tool, metric, or artifact that may not reach the result the user described, or when doing the request as written would leave that result unproved: "A/B test the signup button color" for a conversion problem, "add a cache" for a slow page, "the focused tests passed, announce the release". Also use when a stated constraint contradicts itself, when an unknown fact would have to be invented to finish, or when an external or irreversible step needs an authorization decision. Keywords: right approach, wrong metric, root cause, outcome versus output, what counts as done, proof, is this worth doing. Not for a literal edit, format, translation, or lookup whose method is the deliverable. Not a replacement for the design, debugging, research, or writing method that performs the work. Use the reify skill instead when the request is still too vague to have any method or outcome yet.

Use when work must finish within a stated time limit.

Use when reference images, screenshots, moodboards, style frames, brand boards, cinematic stills, product interface shots, or a live site URL must become a production design system, design tokens, art direction, motion rules, or a YAML style specification. Covers reverse engineering visual references into a deterministic YAML contract with graded confidence, evidence boundaries, and typefaces drawn from the live Google Fonts catalog and ranked as rarely used. Not for generating images or for ordinary frontend work where no reference has to be decoded first.

Use when a claim depends on an agent taking a real action.

Use when a claim depends on people taking a real action.