--- title: "tadeumendonca-skills" description: "The knowledge layer of a public agent-harness reference: 15 dense, opinionated engineering skills covering AWS infrastructure, React/Vite frontends, BFF-on-Lambda backends, CI/CD, the development loop and its quality gat" canonical: https://agentpluginsdirectory.com/plugins/tadeumendonca-skills last-updated: 2026-10-07 --- # tadeumendonca-skills The knowledge layer of a public agent-harness reference: 15 dense, opinionated engineering skills covering AWS infrastructure, React/Vite frontends, BFF-on-Lambda backends, CI/CD, the development loop and its quality gates. Written project-agnostically with / placeholders. This Power ships skills only: the harness's personas, permission hooks, typed commands and merge gates are deliberately not exported. - Slug: tadeumendonca-skills - Publisher: Luiz Tadeu Mendonça - Repository: https://github.com/tedeuxx/tadeumendonca-skills - Manifest: powers/tadeumendonca-skills/plugin.json - Version: 2.0.104 - License: MIT - Category (editorial): devops-cloud - Skills: 15 (agents-configuration, backend, cloud-infrastructure, code-review, content-publishing, definition-of-done, definition-of-ready, devops, documentation-standard, engineering-standards, frontend, planning-poker, published-voice, quality-gates, shell) - MCP servers: 0 - Stars: 0 - Repository created: 2026-06-04 - Repository last pushed: 2026-10-02 - Publisher type: User - Listing: https://agentpluginsdirectory.com/plugins/tadeumendonca-skills - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What tadeumendonca-skills does, in the publisher's words This directory is the Kiro Power package root for tedeuxx/tadeumendonca-skills. It is generated from the repository's own skills/ tree and gated by hooks/scripts/kiro-power.test.sh; editing it by hand will turn that gate red. Edit skills/ /SKILL.md at the repository root instead. > What changed since an earlier release of this file. Earlier releases said the question of > whether a Kiro build implementing the Agent Plugins format would carry agents/ and hooks/ was > unmeasured and claimed in neither direction. It is measured now: against Kiro 1.0.337, on > 2026-08-23: and the answer splits in two: transport yes, activation no (see What this ships > below). The struck text and the full round-by-round history are kept at the source, in the > repository's own README.md. > This file is regenerated and republished on every merge, so it carries current claims only. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/tedeuxx/tadeumendonca-skills/HEAD/powers/tadeumendonca-skills/README.md ## Skills - agents-configuration: Run a slice through this loop's intentional design, its intake chain, state machine, iteration axis and inner-loop steps. Use when picking up a slice, proposing a change to the loop itself, or naming Agent Harness Engineering in public writing. Not the portable judgment (see engineering-standards)… - backend: Implement a BFF-on-Lambda backend as a reference pattern, the Hono modular monolith, cross-cutting middleware (errors, logging, metrics, tracing, audit, action types), Redis cache-aside, config/secrets, the generated OpenAPI contract + Postman tests, notifications, and OG-image + bot-rendering. Us… - cloud-infrastructure: Provision AWS infrastructure in Terraform end to end, one section per service, network, identity and encryption, the config/secrets bus, data stores and cache, storage, compute, API and CDN edge, certificates, DNS, email and event fan-out, and observability. Use when provisioning any AWS resource,… - code-review: Run the author's own completeness pass before opening a merge request, every requirement marked met or unmet, every new assertion mutation-checked, what the change made false, alternative spellings of anything parsed, and the gates run with real output. Use when a slice is finished and not yet sub… - content-publishing: Move a finished piece through the whole lane it travels, the owner's selection, the drafting pair and its two-round bound, the reviewer that REPAIRS a copy defect in place rather than blocking on it, the held preview at the real URL, release, and the social pair in the same batch. Use when a piece… - definition-of-done: Design or evaluate a Definition of Done, and apply THIS loop's own, the criteria a slice calls finished, plus the table naming which of them a gate proves and which nothing does. Use when building a DoD from scratch, checking a slice against this loop's criteria, or diagnosing why review still rea… - definition-of-ready: Set the bar a work item must clear before a builder can pick it up, generically and for THIS loop, what `ready` asserts and which of its criteria anything actually checks. Use when writing acceptance criteria, running intake, sizing a backlog, or diagnosing why in-progress work stalls on undecided… - devops: Operate DevOps for a `` repo: GitHub Actions, Terraform Cloud, branching, the pipeline-only IaC floor, numeric SemVer, the Claude Code GitHub App, and SonarCloud (setup, CI step, gate wiring). Use when wiring a pipeline, granting CI a role, cutting a release, bumping SemVer, or a Sonar ga… - documentation-standard: Write or review documentation for any repo, general docs (README, architecture pages, diagram choice, Markdown + Mermaid only) AND Architecture Decision Records (MADR format, the significance gate, the methodology/product library split, numbering and status, and the current-codebase rule… - engineering-standards: The owner's engineering preferences, portable to any project, two tiers (a non-negotiable floor, a risk-calibrated judgment layer), the eleven principles behind every call, delivered versus hygiene, and the human residual. Use when deciding how much rigor a change deserves, whether something count… - frontend: Build the React + Vite SPA end to end, bootstrap and providers, routing, state ownership (React Query / Zustand / the Cognito SDK), the typed BFF client, auth and cosmetic UI gating, forms, cursor pagination, the custom Tailwind design system and Storybook, async UX states, markdown rendering, SEO… - planning-poker: Run a planning poker estimation round, or diagnose why one produced theater instead of signal. Use when sizing backlog items with a team, choosing between group-consensus estimation and a single person's gut call, or explaining why a session's numbers don't seem to influence anything downstream. Re… - published-voice - quality-gates - shell Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.