davideast
- 18 skills
- 0 followers
- 16 hours ago last updated
- ▌ Tdd · davideast bundleEnforces a disciplined Red-Green-Refactor (TDD) workflow in TypeScript with Vitest. Use when creating new features, fixing bugs, or migrating logic to ensure high-quality, verifiable implementations. Pairs with the typed-service-contract skill.
- ▌ Diataxis Documentation · davideast bundleGuides the creation, restructuring, and review of technical documentation using the Diátaxis framework. Use when writing docs, auditing existing docs for "smells", or structuring complex documentation hierarchies.
- ▌ Pi Coding Agent · davideastBuild sandboxed autonomous agent workflows with @earendil-works/pi-coding-agent and @earendil-works/pi-ai
- ▌ Typed Service Contract · davideast bundleArchitecture standard for building robust, type-safe TypeScript services using the Spec and Handler pattern. Use when building CLIs, libraries, APIs, or complex business logic that requires strict input validation, exhaustive error handling, and testable vertical slices.
- ▌ Coverage Adversary · davideastAdversarially review a pull request that moves a trust number (surface coverage, behavior conformance, rules-language verified coverage, assurance capability status). Use whenever a PR changes any published number, a coverage baseline, a registry row status, a construct's snapshot status, or a denominator. Answers one question - could this number have moved without pyric actually getting better?
- ▌ Playground Prompts · davideastGenerate well-shaped test/demo prompts for the pyric playground agent. Use when the user asks for "more playground prompts", "demo prompts", "test scenarios for the agent", "prompts that exercise X capability", "more prompts like the menu pricing one", or similar requests for short Firestore-rules-focused prompts that hit a specific shape (bounded domain, two-collection data model, rule-enforced security boundary, verifiable by attempting to violate). Catalog of 15 reference prompts plus the structural pattern they share. Invoke via `/playground-prompts` or pick up automatically when the user's ask matches.
- ▌ Firebase Auth Model · davideastDesign or audit Firebase Authentication identity models — provider flows, auth state, custom claims, UID-to-data mapping, and how identities connect to Security Rules. Use when the user needs an auth model, asks who-can-do-what across identities, or wants claims/roles designed or reviewed.
- ▌ Listener Highlights · davideast bundleListener highlights in Pyric — use when explaining Overview or Flow styling, customizing highlight themes, adding Flow Studies treatments, or fixing detached highlight geometry.
- ▌ Rtdb Security Rules · davideastAuthor or audit Realtime Database security rules — cascading read/write access, .validate shape checks, auth expressions, data vs newData semantics. Use when the user works on database.rules.json, asks why an RTDB read/write is allowed or denied, or needs RTDB paths locked down.
- ▌ Firestore Rules Audit · davideastAudit Firestore security rules for public access, semantic errors, unsafe match-block composition, and missing validation. Use when the user asks to review firestore.rules, check rules for vulnerabilities, or explain why a rule allows/denies an operation.
- ▌ Readme Bookstore Test · davideastGenerates and iterates a README that earns the reader's attention progressively (cover → inner flap → reading the book), then verifies every claim and example against the real artifact. Use when writing or reviewing a README or landing page for a library or tool. Includes an iteration ratchet - corrections made during review are captured as general principles, not one-off edits.
- ▌ Improve Firebase · davideast bundleSurvey a whole Firebase application as a senior Firebase engineer, use Pyric's analyzers, sandbox, captured journeys, and verification engines as evidence, then produce a prioritized audit and self-contained implementation plans without changing application source. Use when the user asks to improve, audit, secure, optimize, or production-harden a Firebase app; find Firestore indexes; review Security Rules, auth boundaries, data models, queries, listeners, Firebase AI Logic, Pyric integration configuration, or supported Functions; explain denials; or wants a Firebase improvement roadmap rather than an immediate fix.
- ▌ Firestore Query Indexes · davideastDesign Firestore query shapes and the composite indexes they require — filters, ordering, pagination, collection groups, denormalized reads. Use when the user plans Firestore reads, hits a missing-index error, or asks for firestore.indexes.json.
- ▌ Pyric Inpage Sandbox · davideast bundleEmbed Pyric's in-page Firestore, Storage, and Auth sandbox directly into standalone HTML pages, browser widgets, or UI artifacts without a CLI, backend, or Vite dev server. Use when building client-only prototypes, standalone HTML artifacts, or browser demos that require a functioning local Firestore and Storage database with real-time listeners, security rules, and document seeding. Don't use when developing a standard Vite or Node application (use pyric instead) or when auditing an existing Firebase app (use improve-firebase).
- ▌ Pyric · davideast bundleInstall the current Pyric CLI, start this project's sandbox bridge, and open the app so the in-page sandbox connects. Use before asking an agent to work with Firestore, Auth, or another Firebase service through Pyric.
- ▌ Firebase Audit · davideastAudit a Firebase project's security and data posture — who can access what, what rules/data/auth exist, and where they disagree. Use when the user asks for a Firebase audit, a security review of rules and data, or "find the gaps" across Firestore/RTDB/Auth.
- ▌ Rtdb Data Model · davideastModel Realtime Database structures — flat paths, fan-out writes, index tables, denormalized summaries, .indexOn. Use when the user designs an RTDB tree, complains about slow/overlarge RTDB reads, or asks how to shape data for RTDB queries.
- ▌ Typed Service Contracts · davideast bundleArchitecture standard for building robust, type-safe TypeScript services using the "Spec and Handler" pattern. Use when building CLIs, libraries, or complex business logic.