Receber por email

Design e Frontend

16.414 skills encontradas

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

incident-response

65

Provides incident response best practices covering severity classification, on-call rotation, war room protocols, runbook templates, escalation policies, and blameless postmortems. Use when handling an incident, setting up on-call, writing a postmortem, creating a runbook, configuring PagerDuty or OpsGenie, or building incident management processes.

Design e Frontend por Tibsfox

code-review

65

Reviews code for bugs, style, and best practices. Use when reviewing PRs or checking code quality.

Design e Frontend por Tibsfox

distributed-consensus

65

Distributed consensus algorithms and logical time for cloud and multi-node systems. Covers Lamport clocks, vector clocks, FLP impossibility, Paxos (basic, multi, fast), Raft, Viewstamped Replication, Byzantine fault tolerance basics, quorum reads/writes (N/R/W), leader election, and TLA+ specification style. Use when designing replicated state machines, picking a consensus protocol, reasoning abou

Design e Frontend por Tibsfox

done-retirement

65

Pipeline retirement protocol for completed work items. Implements a 7-stage validate-commit-push-submit-notify-cleanup-terminate pipeline with irreversibility after push. Done means gone.

Design e Frontend por Tibsfox

corporate-finance-basics

65

Corporate finance fundamentals for evaluating business decisions under cost, time, and risk constraints. Covers time value of money, net present value, internal rate of return, payback period, break-even analysis, cost-benefit analysis, debt vs equity, working capital, and the basic financial statements. Use when evaluating an investment, sizing a funding round, structuring a capital stack, or rea

Design e Frontend #ai #api por Tibsfox

contested-claims-in-nutrition

65

A survey of the best-known active scientific controversies in nutrition — saturated fat and cardiovascular disease, dietary cholesterol, low-carb vs low-fat, ultra-processed foods, red meat and cancer, salt and blood pressure, and the replication status of popular single-nutrient claims. Use when a question asks whether a widely reported nutritional claim is settled, or when the department needs t

Design e Frontend #ai #test por Tibsfox

gsd-migrate

65

Migrates existing projects to GSD structure without rewriting history. Activates when user mentions "migrate to GSD", "adopt GSD", "convert project", "brownfield GSD", or wants to add GSD to existing work.

Design e Frontend por Tibsfox

critical-argumentation

65

Practical argument analysis and construction -- how to identify, evaluate, reconstruct, and build real arguments in natural language. Covers argument identification (premises, conclusions, intermediate steps), charity and steel-manning, argument mapping, the distinction between deductive validity and inductive strength, burden of proof, and the rhetorical context in which arguments operate. Use wh

Design e Frontend por Tibsfox

env-setup

65

Environment configuration and secrets management. Use when setting up .env files, managing secrets, or configuring environments.

Design e Frontend por Tibsfox

av-studio

65

Audio/video studio production — multi-track editing, color grading, motion graphics, compositing, live streaming, screen recording, YouTube publishing.

Design e Frontend por Tibsfox

research-mission-generator

65

Package conversation research into a GSD-ready mission package. Produces a three-stage Vision → Research → Mission pipeline as a LaTeX PDF following GSD/NASA SE methodology, designed to be handed to gsd-skill-creator for execution. Use this skill when the user has been discussing, researching, or brainstorming a topic and then asks to turn it into a research mission, research pack, mission package

Design e Frontend #ai #pdf por Tibsfox

session-awareness

65

Project state awareness and session recovery for GSD-managed projects. Use this skill whenever: starting a new work session, resuming after a break, the user asks "where did we leave off" or "what's the current state", before making substantial code changes (to check for existing plans), the user seems disoriented about project status, or when something seems off and STATE.md might have relevant c

Design e Frontend por Tibsfox