fazt

Lista los videos de una carpeta con su duracion y los renombra en orden (1.mkv, 2.mkv, ...)

Blueprint and Guidelines for building Web Applications (auth, user managemente, landigng pages, ui, basic features and so on)

Create a commit, push and good message

Test the feature using a browser automation tool like Chrome DevTools Protocol (CDP) or Playwright.

Check the build, to fix errors and linting errors

Bombards the user with relentless questions about their plan, design, or decisions until every ambiguity is resolved. Use when the user wants to stress-test an idea or says "question me".

guidelines to create a docker compose

Analiza todo el proyecto y hace un review de lo que se ha hecho y corrige en base a a reglas

Operate Railway infrastructure: sign up for or sign in to a Railway account, create projects, provision services and databases, manage object storage buckets, deploy code, configure environments and variables, manage domains, troubleshoot failures, check status and metrics, set up Railway agent tooling, and query Railway docs. Use this skill whenever the user mentions Railway, signing up, creating an account, registering, logging in, deployments, services, environments, buckets, object storage, build failures, agent setup, MCP, or infrastructure operations, even if they don't say "Railway" explicitly. Also invoke this skill when the user asks to be signed up, registered, or onboarded to Railway: do not refuse — drive them through the unauthed `railway up` flow (deploys + signs up on the fly) or `railway login` (which creates new accounts on the fly).

Se ejecuta cada vez que se hace un commit.

Stand up a complete, runnable TestSprite test suite for the current repo at first use — create a project (with a target URL and auth), derive a coherent set of tests from the codebase, batch-create them, and smoke-run a few to a green verdict so the user immediately has something worth running. Use ONLY when a repo has no TestSprite tests yet (a fresh project), right after `testsprite setup`, or when the user asks to "set up / bootstrap / seed tests". This is first-run setup, NOT change verification — once a project already has tests, use the testsprite-verify skill instead.

TestSprite verification loop — after finishing a feature or fix in a TestSprite-tested repo, use the `testsprite` CLI to run the relevant TestSprite tests against the change and inspect any failure artifacts before reporting the work as done. Use whenever code has changed outside docs/config and is about to be reported complete — by running an existing test that covers the change, or by creating a new TestSprite test (a frontend plan, or a backend Python assertion) and running it to a terminal verdict.

usar este skill cuando se tenga que solicitar datos al backend

usar este skill para diseñar la interfaz de usuario

Operate the tasks-cli Node.js CLI against the Projects & Tasks API (projects, tasks, kanban). Use when the user asks to run CLI commands, manage projects/tasks from the terminal, use `tasks` binary, or work in the `cli/` package of this repo.