Explore skills
Showing 14611–14640 of 18608 skills
Adding a variable or secret, 'set up production', a domain or a provider token, 'which database is this', a leaked key: dev and production for an AI-built app, backups, incidents.
phuryn/product-engineering
Stars: 611Claude CodeCodexPrivacy policy, terms, a cookie banner, consent at sign-up, a public front door: legal pages drafted from what the code does, held to it by a test, with the owner's facts and sign-off.
phuryn/product-engineering
Stars: 611Claude CodeCodexBefore adding a remote MCP server or tool to a web product, adding OAuth to it, or listing it in a directory: ship it right the first time, tests included.
phuryn/product-engineering
Stars: 611Claude CodeCodexAdding analytics, session recordings, heatmaps, 'what did users do', Clarity or PostHog: behaviour analytics without analytics cookies, read back by the agent.
phuryn/product-engineering
Stars: 611Claude CodeCodexAdding sign-in, a role, a route that touches data, API tokens, a webhook or job, or 'is this secure': who may do what in a multi-tenant SaaS.
phuryn/product-engineering
Stars: 611Claude CodeCodexA Supabase query, RPC or migration, 'db push', 'supabase link', RLS or grants, a Supabase error: server-only keys, deny-all RLS, migrations via the CLI.
phuryn/product-engineering
Stars: 611Claude CodeCodexAdding transactional or alert email, choosing a provider, 'sent twice', 'never arrived': app email sent once, never lost, with one-click unsubscribe.
phuryn/product-engineering
Stars: 611Claude CodeCodexMandatory for any product's screens, a builder's too, and any mock, prototype or artifact that shows them: its design system, colour, type, components; judging the look.
phuryn/product-engineering
Stars: 611Claude CodeCodexPublishing an app, adding /health or a cron job, 'set up monitoring', 'is it down': content checks, a second location, heartbeats, a tested alert route; Staygreen by default.
phuryn/product-engineering
Stars: 611Claude CodeCodexChoosing the first market or customer segment to win, scored on burning pain, willingness to pay, winnable share and referrals.
phuryn/product-engineering
Stars: 611Claude CodeCodexCompetitive research or a competitive brief: competitors and substitutes, their strengths and weaknesses, where to differentiate.
phuryn/product-engineering
Stars: 611Claude CodeCodexDesigning how a product grows: loops that compound (viral, usage, collaboration, user-generated, referral).
phuryn/product-engineering
Stars: 611Claude CodeCodexExploring customer segments, audiences or new markets: 3-5 segments with their jobs, pains and product fit.
phuryn/product-engineering
Stars: 611Claude CodeCodex'I have an idea', 'is this worth building', 'what next': research it and propose what to build, with sources and key screens to review. Not for agreed changes or bugs.
phuryn/product-engineering
Stars: 611Claude CodeCodexWhere to start, and what comes next, along the product lifecycle: from a new idea, new evidence, an agreed change, a bug or a release to the next step and the skill that does it. Started by name only: /product:start-here in Claude Code, $product:start-here in Codex.
phuryn/product-engineering
Stars: 611Claude CodeCodexComparing a product with competitors or choosing what to be best at: a value curve on one segment's top needs, plus price.
phuryn/product-engineering
Stars: 611Claude CodeCodexCreating or testing a value proposition: the 6-part form (Who, Why, What before, How, What after, Alternatives).
phuryn/product-engineering
Stars: 611Claude CodeCodex'Make this sound human', 'less AI': edit AI-sounding work writing so a careful person could have written it, without changing what it says.
phuryn/product-engineering
Stars: 611Claude CodeCodexThe Balanced Coupling model for software design. Use when: designing modular architectures, evaluating coupling between components, reviewing code modularity, deciding whether to split or merge modules/services, assessing integration patterns, classifying coupling as balanced or unbalanced, applying DDD strategic and tactical patterns, reasoning about cohesion vs coupling trade-offs, identifying distributed monolith risks, or explaining why a system is hard to change. Provides the three-dimensional framework (integration strength, distance, volatility) and the balance rule for making coupling decisions.
vladikk/modularity
Stars: 604Claude CodeCodexDesigns modular high-level architectures from functional requirements and produces design documents for each module. Use when designing a new system, creating architecture documentation, or producing module-level design specs with integration contracts and test specifications.
vladikk/modularity
Stars: 604Claude CodeCodexProduces modularity review documents in both Markdown and HTML formats. Use when writing the final review output from a modularity analysis.
vladikk/modularity
Stars: 604Claude CodeCodexAnalyzes a codebase's modularity imbalances using the Balanced Coupling model and produces a review of design issues. Use when reviewing existing code for coupling problems, assessing architecture quality, identifying distributed monolith risks, or finding areas where changes are unexpectedly expensive.
vladikk/modularity
Stars: 604Claude CodeCodexDefines measurable architecture drivers and constraints before system design; edits architecture docs only.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexDocuments current architecture from implementation evidence; does not propose a target or audit fitness.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexDesigns target system boundaries, contracts and tradeoffs from requirements; does not plan tasks or implement.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexRecords one architecture decision with alternatives, consequences and status; does not design the whole system.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexCreates evidence-backed current or target architecture diagrams; not UI design.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexPlans architecture migrations with compatibility, data safety, rollout and recovery; does not execute them.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexBuilds dependency-ordered delivery plans from requirements and repository evidence; read-only.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodexPlans risk-based test portfolios and acceptance evidence; does not write or execute tests.
levnikolaevich/claude-code-skills
Stars: 596Claude CodeCodex