Showing 31621–31650 of 77205 skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Tohuhono/Oberon
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Tohuhono/Oberon
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Tohuhono/Oberon
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
Tohuhono/Oberon
Break a plan, spec, or conversation into tracer-bullet GitHub issues for Oberon, with category and state labels, sub-issues, and blocking relationships.
Tohuhono/Oberon
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Tohuhono/Oberon
中文去 AI 腔、恢复自然表达。用于小说创作(人物、对白、场景、叙事节奏)、日常对话、代码沟通、论述成文清理与小说成稿清理。学术论文、公文、法律文书、营销文案、演讲稿默认不进入清理;用户点名按本 skill 清理时除外。
chengzhi-c/natural-talk
Turn your AI session into an autonomous SaaS and software engineering studio with 50 specialized agents, 108 workflow skills (/saas-*), 28 director gates, and complete architecture across Next.js, FastAPI, Supabase, Tailwind, and Stripe.
Basinfy/Basinfy-SaaS-Studio
Create an ADR documenting a technical decision: context, alternatives considered, consequences.
Basinfy/Basinfy-SaaS-Studio
Audit assets against naming conventions, file size budgets, format standards. Finds orphaned assets, missing references.
Basinfy/Basinfy-SaaS-Studio
Author per-asset visual specs, SVG dimensions, and generation prompts from PRDs and design tokens. After design tokens.
Basinfy/Basinfy-SaaS-Studio
Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.
Basinfy/Basinfy-SaaS-Studio
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
Basinfy/Basinfy-SaaS-Studio
Auto-generate a changelog from git commits and sprint data. Internal and user-facing versions.
Basinfy/Basinfy-SaaS-Studio
Architectural code review — coding standards, SOLID, testability, performance concerns.
Basinfy/Basinfy-SaaS-Studio
Scan PRDs against the entity registry for cross-document conflicts. Index-first approach (Basinfy when .basinfy/ exists, else Grep) targets conflicting sections.
Basinfy/Basinfy-SaaS-Studio
Builds a short list of must-do and never-do coding rules per system from accepted ADRs. Use when the user wants programmer rules or a quick reference sheet from the ADRs, or needs it regenerated after ADR changes.
Basinfy/Basinfy-SaaS-Studio
Turns the PRDs and architecture into epics, one per architectural module. Use when the user wants to break the application into epics or plan the work before writing stories. Not for splitting one epic into stories.
Basinfy/Basinfy-SaaS-Studio
Breaks one epic into implementable stories with acceptance criteria. Use when the user wants stories for an epic or the next batch of work to build. Not for turning the whole design into epics.
Basinfy/Basinfy-SaaS-Studio
Reviews one design document for completeness, internal consistency, implementability, and design standards. Before handing to programmers.
Basinfy/Basinfy-SaaS-Studio
Implements one story in code with tests, following its ADRs. Use when the user says to build, implement or start working on a story. Not for checking readiness beforehand or closing the story after.
Basinfy/Basinfy-SaaS-Studio
Estimate task effort from complexity, dependencies, velocity, risk. Structured estimate with confidence levels.
Basinfy/Basinfy-SaaS-Studio
What should I do next? Use when stuck or you don't know what to do.
Basinfy/Basinfy-SaaS-Studio
Emergency fix bypassing normal sprint process — hotfix branch, approvals tracked, backport verified, full audit trail.
Basinfy/Basinfy-SaaS-Studio
Launch readiness across every department: code, content, store, marketing, community, infrastructure, legal, go/no-go sign-offs.
Basinfy/Basinfy-SaaS-Studio
Apply anonymization (Art. 5, XI) and pseudonymization (Art. 13, §4) techniques to take data out of LGPD scope or reduce risk in analytics pipelines. Use when user asks 'anonimizar', 'pseudonimizar', 'k-anonymity', 'differential privacy', 'tokenização', 'analytics LGPD', or designing analytics/ML pipelines.
Basinfy/Basinfy-SaaS-Studio
Maestro orchestrator for end-to-end LGPD (Lei 13.709/2018) compliance in a software project. Use for "como estamos de LGPD", "audite LGPD", "nos deixe LGPD seguros", "gap analysis LGPD", "compliance LGPD", "auditar privacidade", "LGPD do projeto", or any request to assess, implement, or retrofit privacy compliance — including English phrasings like "are we privacy-safe", "audit our privacy", or "we collect personal data, what do we need". Chains specialized sub-skills (data mapping, legal basis, consent, DSAR, incident response, ROPA, RIPD, retention, vendor audit, DPA, international transfer, encarregado, and ECA Digital / Lei 15.211/2025 for platforms with minors) and produces versioned artifacts under .lgpd/. Trigger even when the word "LGPD" is not used.
Basinfy/Basinfy-SaaS-Studio
Design and implement immutable, hash-chained audit logging for accountability (LGPD Art. 6, X) and incident registration (Res. 15/2024 Art. 10, 5-year retention). Use when user asks 'audit log', 'log de auditoria', 'logging LGPD', 'accountability log', or as part of audit pipeline. Outputs schema + middleware patterns for Next.js.
Basinfy/Basinfy-SaaS-Studio
Design the database schema for a versioned, append-only consent ledger that satisfies LGPD Art. 8 (free, informed, unambiguous consent for a specific purpose) and Art. 9 (information rights). Use when user asks for "consent schema", "consent ledger", "schema de consentimento", "Prisma consentimento", "consent management", or is integrating consent capture with Better Auth, NextAuth, Clerk, or any auth library. Outputs a Prisma schema + integration spec. Also produces the structure needed to support DSAR revocation (Art. 18, IX).
Basinfy/Basinfy-SaaS-Studio
Draft and review Data Processing Agreements (DPA) with operadores under LGPD Art. 39. Use when user mentions 'DPA', 'contrato com operador', 'cláusulas LGPD', 'data processing agreement', or onboarding a new third-party service (analytics, cloud, payment, email, SMS, observability). Outputs DPA template + per-vendor sheets in `.lgpd/vendors/`.
Basinfy/Basinfy-SaaS-Studio