Menú
Skills en este repositorio
SkillsMP ha recopilado 97 skills de blackprince001/skills. Abre una skill para revisar su origen y sus detalles.
blackprince001/skillsMostrando 40 de 97 skills recopiladas.
Always-on security mindset for every project and phase: hostile inputs, explicit trust boundaries, least privilege, secret hygiene, sensitive-data defaults, abuse cases, and escalation triggers before secure-coding or platform-specific security skills add…
Idioma del texto original: inglés
Use when naming, writing, reviewing, or connecting product-management artifacts such as product briefs, PRDs, requirements, non-functional requirements, roadmaps, initiatives, epics, features, stories, tasks, bugs, risks, decisions, and issue states;…
Idioma del texto original: inglés
Use when writing, editing, or reviewing godfile skills themselves — the principles that make a skill predictable for agents (descriptions as triggers, information hierarchy, leading words, pruning, failure modes).
Idioma del texto original: inglés
Use when establishing a project's reusable visual foundations before broad UI work—token hierarchy, typography, semantic color, spacing, elevation, theming, component primitives, and the rules that keep design and code aligned.
Idioma del texto original: inglés
Use when setting up or changing project configuration, local environments, CI/CD credentials, or secrets—separate configuration from secrets, validate at startup, use least-privilege delivery, prevent leaks, and plan rotation.
Idioma del texto original: inglés
Use when turning an idea into actionable work — refining vague ideas (divergent/convergent), stress-testing a plan by interview (grilling), writing gated specs, breaking work into tracer-bullet tickets with blocking edges and checkpoints, charting oversized…
Idioma del texto original: inglés
Use when standing up or hardening a repo, or making any code change flow through git — trunk-based workflow, atomic commits with why-messages, worktrees for parallel agents, pre-commit hooks, and git-safety guardrails.
Idioma del texto original: inglés
Use when pinning down what a project is before building — domain modeling and ubiquitous language (CONTEXT.md glossary), ADRs, the planning document (user classes, scenarios, competition, community design), and NFR capture across the fourteen quality…
Idioma del texto original: inglés
Use when choosing a stack, system architecture, architectural pattern, or design-pattern direction before building; applies problem-first trade-off evaluation, defaults to simple modular designs, records rejected alternatives, and uses the bundled…
Idioma del texto original: inglés
Use when someone describes a motion effect vaguely and needs its precise name to write a design brief, prompt, or implementation specification; this skill names effects, not designs them.
Idioma del texto original: inglés
Design product copy and localization-ready interfaces before implementation. Use when defining tone, labels, errors, empty states, locale scope, regional variants, text expansion, RTL behavior, culturally appropriate content, format requirements, or…
Idioma del texto original: inglés
Use when designing or implementing a polished interface: decide whether motion earns its place, tune component feedback, transitions, spacing, depth, and the small details that make a UI feel deliberate.
Idioma del texto original: inglés
Use when designing or reviewing drag, swipe, sheets, drawers, spring motion, momentum, or any interaction the user can interrupt or reverse while it is moving.
Idioma del texto original: inglés
Design readable, professional typography for interfaces and content: typeface choice, pairing, hierarchy, type scale, line length, line height, spacing, responsive text, font licensing, multilingual glyph coverage, typographic correctness, and typography…
Idioma del texto original: inglés
Use when structuring a product's UX or answering a design question with a throwaway prototype — logic prototypes (interactive TUI over a pure state module) or UI prototypes (radically different variants switched by URL param).
Idioma del texto original: inglés
Use when implementing accessibility in code: semantics, accessible names, focus management, keyboard behavior, dynamic announcements, forms, media, reduced motion, pointer alternatives, and robust custom controls.
Idioma del texto original: inglés
Implement internationalization and localization in code: string externalization, ICU messages, CLDR plural rules, locale detection, fallback chains, RTL plumbing, localized formatting, translation files, namespace loading, hreflang, pseudolocalization, and…
Idioma del texto original: inglés
Use when building for performance targets — the six measurable characteristics (response time, throughput, latency, scalability, resource utilization, stability) and the implementation levers from algorithms through caching, database, network, and…
Idioma del texto original: inglés
Use when writing any code that touches user input, auth, sensitive data, or external services — threat-model first (STRIDE), the always/ask-first/never boundary tiers, OWASP injection/XSS/SSRF/access-control patterns, secrets and supply-chain hygiene.
Idioma del texto original: inglés
Design and implement application state, data fetching, caching, optimistic updates, offline sync, conflict handling, forms, validation, input metering, and server/client data boundaries across web, mobile, backend, and UI-heavy applications.
Idioma del texto original: inglés
Use when turning settled interface designs into production components—component boundaries and APIs, composition, token consumption, styling, accessible states, motion implementation, and reuse without premature abstraction.
Idioma del texto original: inglés
Use before shipping any user-facing change to prove accessibility through automated checks plus manual keyboard, assistive-technology, contrast, resize/reflow, reduced-motion, and error-recovery passes; record blockers and evidence.
Idioma del texto original: inglés
Use for a motion-only review of UI code or a rendered interaction. Enforce purpose, frequency-appropriate timing, responsiveness, interruptibility, performance, and reduced-motion support; do not use as a general code-review skill.
Idioma del texto original: inglés
Use when proving performance targets are met before ship — continuous performance tests in the sprint cycle so code can't silently regress, load testing against stated conditions, and metric gates derived from the NFR criteria.
Idioma del texto original: inglés
Use when verifying anything that renders in a browser — agent-driven browser verification (Chrome DevTools MCP), structured visual-feedback annotations (Agentation), UI/network/performance debugging, screenshot comparison, clean-console standard, and treating…
Idioma del texto original: inglés
Use when planning how a change reaches users — feature flags (deploy ≠ release, flags must die), staged rollout with metric thresholds, rollback plans written before deploy, and expand/contract schema migrations.
Idioma del texto original: inglés
Use when building or changing release automation—create one reproducible artifact, promote it through environments with explicit gates, protect credentials and approvals, preserve provenance, and keep rollback possible.
Idioma del texto original: inglés
Use when cutting a release, choosing a version bump, tagging, or writing a changelog — semver as a promise to consumers, when-unsure-assume-breaking, tags as source of truth, human-curated changelogs written with the change.
Idioma del texto original: inglés
Use when creating, organizing, or updating project documentation and knowledge bases in any project — structure knowledge as an OKF bundle (markdown + frontmatter, index.md, log.md, cross-links) so both humans and agents can read, traverse, and maintain it.
Idioma del texto original: inglés
Use when a production service, user journey, security posture, or reliability target is failing—declare and coordinate the incident, mitigate user harm first, communicate clearly, preserve evidence, restore safely, and turn learning into owned follow-up.
Idioma del texto original: inglés
Use when keeping shipped systems healthy — diagnosing hard bugs and performance regressions (build a tight feedback loop first), scanning for architecture-deepening refactors, dependency updates, and debt.
Idioma del texto original: inglés
Use when deprecating or removing systems, APIs, or features — code is a liability, the deprecation decision questions, advisory vs compulsory, strangler/adapter migration patterns, zombie code, and the removal checklist.
Idioma del texto original: inglés
Use when designing or evolving a reusable library's public API, types, extension points, errors, defaults, or documentation; extends core contract and architecture rules for code consumed inside other programs.
Idioma del texto original: inglés
Use when packaging, publishing, versioning, deprecating, or changing compatibility for a reusable library; extends core release rules with package formats, public API compatibility, support matrices, and consumer verification.
Idioma del texto original: inglés
Use when choosing native iOS, native Android, React Native, or Expo; setting minimum OS and device support; structuring a mobile project; or deciding where platform conventions and platform-specific behavior should differ.
Idioma del texto original: inglés
Use when designing or implementing mobile animations, transitions, direct-manipulation gestures, gesture conflicts, springs, scroll-linked effects, haptics, or reduced-motion behavior in Expo, React Native, SwiftUI, UIKit, Compose, or Android Views.
Idioma del texto original: inglés
Use when designing or implementing mobile screen composition, stacks, tabs, modals, sheets, back behavior, deep-linked routes, lists, safe areas, keyboards, or adaptive phone, tablet, foldable, and multi-window layouts.
Idioma del texto original: inglés
Use when implementing mobile offline behavior, local persistence and sync, permissions, background work, notifications, deep links, app clips, native modules, battery-sensitive work, device storage, or interrupted lifecycle behavior.
Idioma del texto original: inglés
Use when implementing or auditing VoiceOver, TalkBack, Switch Control, Voice Control, Dynamic Type or font scaling, mobile focus and semantics, system accessibility settings, app language, locale formatting, plurals, RTL, or localized mobile assets in Expo,…
Idioma del texto original: inglés
Use when preparing, signing, beta testing, submitting, reviewing, staging, monitoring, rolling back, or updating iOS and Android apps through TestFlight, App Store Connect, Google Play, EAS Build/Submit/Update, or native release pipelines.
Idioma del texto original: inglés