← all publishers

danielteles

@danielteles source repo

Report this profile Claim this profile

• 14 skills
• 0 followers
• 8 hours ago last updated

1. ▌
   Skill Name · danielteles bundle

   <One or two sentences: what this skill governs and the form of guidance it gives — write, review, refactor, migrate.> <One sentence: the task types it serves.> Builds on <`sibling`, `sibling`>. Use it when the user mentions <keyword>, <keyword>, <keyword>, or <keyword>.
   0 installs
2. ▌
   Vue · danielteles bundle

   Modern Vue 3 conventions for writing, reviewing, refactoring, or migrating Vue: `<script setup>` and the Composition API, `defineProps` / `defineEmits` / `defineModel`, `ref` vs `reactive` and reactivity-loss caveats, composables for shared logic, `provide` / `inject` and Pinia within the state tiers, templates and keyed lists, `<Suspense>` and async components, the Nuxt server boundary, and testing by role. Builds on `core-typescript` and `architecture-and-design`. Use it when the user mentions Vue, Nuxt, `script setup`, Composition API, `ref`, `reactive`, `computed`, `watch`, composables, Pinia, `defineModel`, `v-model`, `provide`/`inject`, or hydration mismatch.
   0 installs
3. ▌
   React · danielteles bundle

   Modern React conventions for writing, reviewing, refactoring, or migrating React: render purity, the Rules of Hooks, "you might not need an Effect", state placement, refs, context, Suspense data fetching, Actions and form state, Server and Client Components, the React Compiler, testing by role. Builds on `core-typescript` and `architecture-and-design`. Use it when the user mentions React, hooks, useEffect, useState, re-renders, Server Components, "use client", Suspense, the React Compiler, useActionState, context, or forwardRef.
   0 installs
4. ▌
   Angular · danielteles bundle

   Modern Angular conventions for writing, reviewing, refactoring, or migrating Angular: standalone components, `OnPush` and signals, `input()` / `output()` / `model()`, `@if` / `@for` / `@switch` control flow, `inject()` and functional providers, functional guards and interceptors, Signal Forms and typed reactive forms, lazy routing, zoneless-ready change detection and SSR, testing by role. Builds on `core-typescript` and `architecture-and-design`. Use it when the user mentions Angular, signals, `computed`, `effect`, standalone, `OnPush`, control flow, `inject`, RxJS, reactive forms, change detection, zoneless, `NgModule`, or `ng generate`.
   0 installs
5. ▌
   E2e Testing · danielteles bundle

   Framework-neutral standards for end-to-end browser tests with Playwright or Cypress: role-based user-facing selectors, per-worker and per-test data isolation, network interception, web-first retrying assertions instead of fixed waits, a retry and sharding policy, flake triage to a root cause, and keeping the suite a thin layer of critical journeys. Composes with `test-quality` for the quality of each individual test. Use it when the user mentions end-to-end tests, E2E, Playwright, Cypress, browser tests, "flaky test", getByRole, test-id, network mocking, test retries, sharding, or "the e2e suite is slow".
   0 installs
6. ▌
   Test Quality · danielteles bundle

   Framework-neutral standards for the quality of an individual automated test in TypeScript: assert on behavior not implementation, meaningful assertions, one outcome-named scenario per test, builders over shared fixtures, test doubles that earn their place, deterministic order-independent tests, coverage read as a map of the unverified. Use it when writing tests for new or changed code, reviewing the tests in a pull request, or fixing a weak, brittle, or flaky test — or when the user says "test quality", "unit test review", "these tests are brittle", "flaky test", "over-mocking", "testing implementation details", "AAA", "arrange act assert", or "assert on behavior".
   0 installs
7. ▌
   Accessibility · danielteles bundle

   Web accessibility as a framework-neutral review lens for building or reviewing UI, grounded in the W3C WAI: WCAG 2.2 level AA, WAI-ARIA, and the ARIA Authoring Practices Guide. Semantic HTML and structure, accessible names and ARIA, keyboard and focus, forms, perceivable content (text alternatives, contrast, motion, zoom), live regions and SPA route announcements, a11y testing. Composes with `react`, `angular`, and `vue` for the framework mechanism. Use it when the user says "accessibility", "a11y", "WCAG", "ARIA", "screen reader", "keyboard navigation", "focus", "contrast", "axe", "landmark", or "WAI".
   0 installs
8. ▌
   Core Typescript · danielteles bundle

   Language-level TypeScript conventions for every project, framework or not — compiler strictness, banning unsafe types, inference and `satisfies`, discriminated unions and branded ids, narrowing, generics, utility types, nullability, async, errors as `unknown`, module and language hygiene. The base skill that `react`, `angular`, `vue`, and `architecture-and-design` build on. Use it when writing, reviewing, or refactoring TypeScript, setting up `tsconfig.json`, or when the user says "TypeScript", "tsconfig", "strict mode", "type error", "any", "generics", "type safety", "utility types", "discriminated union", or "narrowing".
   0 installs
9. ▌
   Web Performance · danielteles bundle

   A framework-neutral review lens for the loading and runtime performance of a web UI: Core Web Vitals budgets, diagnosing and fixing LCP, INP, and CLS, JavaScript bundle analysis and a code-splitting policy, image and font loading, hydration cost, and field measurement (RUM) with regression gating. Composes with `react`, `angular`, and `vue` for the framework rendering API and with `architecture-and-design` for data and state strategy. Use it when the user mentions performance, Core Web Vitals, LCP, INP, CLS, Lighthouse, bundle size, code splitting, lazy loading, hydration, "slow page", "large bundle", web-vitals, or RUM.
   0 installs
10. ▌
    Component API Design · danielteles bundle

    Framework-neutral standards for the public API of a reusable UI component: a minimal and stable props contract, slots and composition versus configuration props, controlled and uncontrolled value pairs, the compound-component pattern, and evolving a shared component without breaking its consumers. Sits between `architecture-and-design` and the framework skills. Use it when the user mentions component API, props design, a component library or design system, slots, render props, controlled vs uncontrolled, compound components, a "boolean prop explosion", or versioning a shared component.
    0 installs
11. ▌
    Frontend Code Review · danielteles bundle

    A meta skill that orchestrates a frontend code review: given a diff, it picks which of the other skills apply, runs them in a sensible order, merges their findings into one ordered list, and de-duplicates an issue that two skills report. It holds no engineering rules of its own — it routes to `core-typescript`, `architecture-and-design`, the framework skills, and the lenses. Use it when the user asks for a full code review of a pull request or a diff, says "review this change", "run all the skills", "which skills apply here", or wants findings from several skills combined without duplication.
    0 installs
12. ▌
    I18N And Localization · danielteles bundle

    A framework-neutral review lens for internationalizing a web UI: ICU MessageFormat messages keyed by meaning, CLDR plural and gender selection, locale-aware date, number, currency, and list formatting with `Intl`, right-to-left and bidirectional text, locale in the URL with negotiation and `hreflang`, and the message-catalog lifecycle (fallback, lazy loading, pseudo-localization). Composes with `react`, `angular`, and `vue` for the i18n library API. Use it when the user mentions i18n, l10n, internationalization, localization, translation, ICU MessageFormat, plurals, `Intl`, RTL, bidi, locale routing, `hreflang`, `Accept-Language`, or a message catalog.
    0 installs
13. ▌
    Architecture And Design · danielteles bundle

    Framework-neutral architecture and design standards for frontend engineering in TypeScript (React, Angular, Vue, or any component framework): SOLID and clean code, clean architecture and layer boundaries, feature-first structure, the adapter/repository pattern, state tiers and data fetching, security, testing strategy, DDD tactical patterns, micro-frontends, forms. Use it when generating a component or module, refactoring frontend code, reviewing a pull request, or making an architecture decision, or when the user says "code review", "clean architecture", "SOLID", "design pattern", "DDD", "bounded context", "micro-frontend", "data fetching", "form validation", or "how should I structure this".
    0 installs
14. ▌
    Styling And Design Tokens · danielteles bundle

    A framework-neutral review lens for CSS architecture and design tokens when building or reviewing web UI: cascade layers and flat specificity, a primitive/semantic/component token pipeline, theming and dark mode by token redefinition, the CSS Modules vs utility vs CSS-in-JS decision, intrinsic responsive layout, container queries, and fluid type and spacing. Composes with `react`, `angular`, `vue`, and `accessibility`. Use it when the user mentions CSS, styling, design tokens, theming, dark mode, a design system, container queries, media queries, responsive layout, fluid type, "clamp", Tailwind, CSS Modules, CSS-in-JS, cascade layers, or "@layer".
    0 installs