← all publishers

le-19-stvn

@le-19-stvn source repo

Report this profile Claim this profile

• 19 skills
• 0 followers
• 19 hours ago last updated

1. ▌
   New Project · le-19-stvn

   The router. Starts any new project cleanly — app, website, brand, or content — by detecting its type, triggering the taste layer, building a project charter, and recommending which department plugins to enable. Use this whenever the user begins a project or says "new project", "let's start", "kick off", "set up". This is the entry point of the whole stack.
   0
   installs
2. ▌
   Taste Layer · le-19-stvn

   Capture the human point of view for a project before any generation happens, and enforce it afterwards. Use this skill at the start of any creative or product work — design, brand, UI, copy, content, naming — and whenever a request would otherwise be answered with a generic default. Trigger when the user starts a project, asks for design/brand/content, or says things like "make it good", "not generic", "with taste". Produces and maintains a TASTE.md the whole stack reads.
   0
   installs
3. ▌
   Project Charter · le-19-stvn

   Produce and maintain the project's CLAUDE.md — the single source of truth every session reads. Use this right after project type and taste are established, or whenever project conventions, stack, or constraints need to be recorded. Trigger on "set up CLAUDE.md", "project rules", "conventions", or as step 3 of new-project.
   0
   installs
4. ▌
   Legal Doc · le-19-stvn

   Draft or review common legal documents from templates, bound to the project's declared legal context. Use when creating or checking an NDA, ToS/CGU/CGV, privacy policy, legal notices (mentions légales), or cookie notice for a creative-stack project. Trigger on NDA, terms of service, privacy policy, legal notice, cookie policy, contract review. Reads LEGAL-CONTEXT.md, CLAUDE.md, and TASTE.md first. Informational templates only; not legal advice.
   0
   installs
5. ▌
   UI System · le-19-stvn

   Build a coherent design system — tokens, components, spacing and type scales — from the project's brand and taste. Use when the user needs a design system, component library, style tokens, or consistent UI foundations across a product. Trigger on design system, tokens, component library, style guide (for product UI). Reads TASTE.md and BRAND.md.
   0
   installs
6. ▌
   Tech Charter · le-19-stvn

   Force a decided technical stack instead of a defaulted one, and write it to STACK.md. Use when starting to build an app or service, choosing a framework/runtime/data layer, or when the user asks "what stack", "what should I use", "set up the project". This is the dev department's anti-slop core — the STACK.md it produces is what feature-build and dev-critic hold the code to.
   0
   installs
7. ▌
   Feature Build · le-19-stvn

   Build a feature bound to the project's decided stack and taste, delegating to language-specific reviewers when available. Use when implementing a feature, endpoint, module, or fixing a bug in a creative-stack project. Trigger on build, implement, add feature, write the code. Reads STACK.md, CLAUDE.md, and TASTE.md first.
   0
   installs
8. ▌
   Security Review · le-19-stvn

   End-of-development defensive hardening audit for a web project — scored, with fixes. Runs a defensive configuration checklist (security headers, CORS, TLS, file exposure, form protection, cache/SRI/security.txt), scores the result out of 100 by severity, and proposes config diffs to apply after human review. Use when hardening before launch, or when the user asks "is this secure to ship", "security audit", "hardening review", "check the headers/CORS/TLS". This is a NON-INTRUSIVE configuration review, not a penetration test.
   0
   installs
9. ▌
   Legal Context · le-19-stvn

   Force the project's legal ground to be declared instead of assumed, and write it to LEGAL-CONTEXT.md. Use before drafting or reviewing any legal document, or when the user asks "do we need an NDA / ToS / privacy policy", "legal setup", "what jurisdiction". This is the legal department's core — the LEGAL-CONTEXT.md it produces is what legal-doc and legal-critic hold every document to. Templates and structure only; not legal advice.
   0
   installs
10. ▌
    Content Piece · le-19-stvn

    Draft a single content piece the human has chosen as worth existing — bound to the editorial strategy, positioning, and voice. Use when writing an article, essay, newsletter, thread, tutorial, or doc for a creative-stack project. Trigger on content, article, post, newsletter, blog, write a piece. Reads CONTENT-STRATEGY.md, POSITIONING.md, and BRAND.md first. Never batch-generates volume on autopilot.
    0
    installs
11. ▌
    Brand Identity · le-19-stvn

    Build a brand identity — positioning, personality, palette, typography, logo direction, and tone — bound to the project's declared taste. Use when the user works on a brand, visual identity, style guide, charte graphique, naming, or logo. Trigger on brand, identity, palette, typography, logo, tone of voice. Reads TASTE.md first and produces BRAND.md.
    0
    installs
12. ▌
    Copywriting · le-19-stvn

    Write marketing copy — landing pages, emails, ads, launch announcements — bound to the project's positioning and taste, delegating to marketing/SEO agents when available. Use when writing or improving any customer-facing marketing copy, or when the user asks for a headline, landing page, campaign, or launch. Trigger on copy, headline, landing, email, ad, launch, campaign. Platform-native social posts belong to the social-post skill, not this one. Reads POSITIONING.md, TASTE.md, and BRAND.md first.
    0
    installs
13. ▌
    Positioning · le-19-stvn

    Force a decided market position instead of generic "for everyone" messaging, and write it to POSITIONING.md. Use before writing any marketing copy, landing page, launch, or campaign, or when the user asks "how do we position this", "what's the message", "who is this for". This is the marketing department's anti-slop core — the POSITIONING.md it produces is what copywriting and marketing-critic hold every word to.
    0
    installs
14. ▌
    Social Post · le-19-stvn bundle

    Write platform-native social posts — LinkedIn, Reddit, X/Twitter, Instagram — adapting the form to each channel while holding the position declared in POSITIONING.md. Use when writing or adapting a post, thread, carousel, or comment for a social network, or turning an existing article into channel-native posts. Trigger on LinkedIn, Reddit, X, Twitter, Instagram, post, thread, carousel, social. Reads POSITIONING.md first and refuses to write without it.
    0
    installs
15. ▌
    Frontend Design · le-19-stvn

    Design and build distinctive frontend UI that doesn't look templated, bound to the project's taste and brand. Use when building UI, a component, a page, a React/Tailwind interface, or when the user asks to make something look better or less generic. Trigger on frontend, UI, component, layout, styling. Reads TASTE.md and BRAND.md first.
    0
    installs
16. ▌
    Financial Model · le-19-stvn

    Build pricing, unit economics, projections, and pitch-deck figures from the project's declared assumptions. Use when building a financial model, setting a price, computing unit economics, forecasting, or preparing deck numbers for a creative-stack project. Trigger on pricing, model, unit economics, projections, forecast, runway, pitch deck numbers. Reads ASSUMPTIONS.md, CLAUDE.md, and TASTE.md first. Builds only from declared inputs; never gives personalized investment advice.
    0
    installs
17. ▌
    Content Strategy · le-19-stvn

    Force a decided editorial strategy instead of publishing whatever fills the calendar, and write it to CONTENT-STRATEGY.md. Use before producing any content, or when the user asks "what should we publish", "content plan", "editorial calendar", "what topics". This is the content department's anti-slop core — the CONTENT-STRATEGY.md it produces is what content-piece and content-critic hold every piece to.
    0
    installs
18. ▌
    Campaign Build · le-19-stvn

    Plan a marketing campaign or launch — the objective, audience, channel mix, asset list, and sequence — bound to the project's positioning. Use when planning a launch, a multi-asset campaign, an email sequence, or a channel plan. Trigger on campaign, launch, go-to-market, sequence, channel plan, rollout. Reads POSITIONING.md, TASTE.md, and CLAUDE.md first. Plans the campaign; hands each asset's actual copy to the copywriting skill.
    0
    installs
19. ▌
    Financial Assumptions · le-19-stvn

    Force every financial number to rest on a declared assumption instead of a default or a guess, and write them to ASSUMPTIONS.md. Use before building any pricing, model, forecast, or pitch-deck financials, or when the user asks "what should we charge", "build a model", "what are the projections", "TAM". This is the finance department's anti-slop core — the ASSUMPTIONS.md it produces is what financial-model and finance-critic hold every number to.
    0
    installs