yumaitau
- 8 skills
- 0 followers
- 1 day ago last updated
- ▌ Dot Product · yumaitau bundleUse this skill to analyse an existing codebase and produce a `.product/` folder of sales-oriented knowledge files describing what the product does, who it serves, and how it competes. Output is consumed by sales reps, marketing, demo builders, and AI sales agents — not engineers. Trigger when the user asks to "extract product features", "build a product profile", "generate sales docs from the code", "build a sales agent for this product", "what does this app actually do", "summarise this codebase for sales", or asks for files like FEATURES.md, USE_CASES.md, or a product knowledge base. Also use when onboarding a new product into a sales motion or building an AI agent that needs to pitch, qualify, or answer questions about the product. Pairs with human-copy-style and portfolio-copywriter for downstream copy work.
- ▌ Yuma It Context · yumaitauCompany facts, positioning, and claim boundaries for Yuma IT itself, not a client's product. Supplies the legal and procurement record (entity name, ABN, address, Supply Nation certification), services, audience-specific proof points, and the rules on which past work Yuma may claim as its own. Use when writing or editing anything about Yuma IT — website pages, capability statements, tender and grant responses, proposals, social profiles, team bios, repository descriptions, or an introduction email. Use when filling a supplier form, vendor questionnaire, or procurement portal for Yuma. Use before repeating any claim about a named program such as the National Koala Monitoring Program, SpaceCows, or Healthy Country AI, because company work and founder work need different wording. Pairs with human-copy-style and the copywriter skills, which own voice and structure while this owns the facts. Not for mining a codebase for product knowledge, whether the product is a client's or Yuma's own, which is dot-product.
- ▌ Human Copy Style · yumaitauUse this skill whenever writing or editing any customer-facing copy, including marketing text, UI microcopy, emails, landing pages, product descriptions, taglines, blog posts, social posts, or announcements that should sound like a person wrote them. Trigger this even for short asks like "rewrite this product description," "tighten this," or "punch this up," and for any task where the output will be read by customers or prospects. Enforces plainspoken language, varied sentence rhythm, Australian spelling, and removal of common AI tells (em dashes, emojis, filler transitions, generic hype, triple-adjective chains, rule-of-three slogans, and hedged verbs). For website page copy it pairs with portfolio-copywriter, and for campaign pieces like emails, announcements, social posts, and ads with campaign-copywriter; those skills own positioning, structure, proof, and SEO while this skill owns voice. Not for developer documentation, code comments, or legal wording.
- ▌ Australian English · yumaitauEnforces Australian English in all prose output, including documentation, READMEs, changelogs, UI text, error messages, emails, reports, code comments, and commit messages. Use whenever writing or editing prose in a project that targets an Australian audience or team, whenever the user asks for Australian English, AU spelling, or -ise endings, or complains about American spellings, and even when nobody mentions spelling at all, since agents default to US English. Covers the tricky noun/verb pairs (licence/license, practice/practise, program/programme), the -ise, -our, and -re families, and the hard boundary that code identifiers, API names, package names, and conventional filenames like LICENSE always keep their original spelling. Every other skill in this pack requires Australian English and defers here for the detail; this skill is also primary for developer-facing prose. Not for projects with a documented US or British English convention, and never for respelling quoted text or code.
- ▌ Laravel Gate Audit · yumaitauUse this skill when auditing a Laravel application for authorization gate and policy usage, especially requests like "find missing gates", "audit Gate::allows", "check @can permissions", "verify policies", or "find undefined abilities". It traces ability usage across controllers, models, Blade, Livewire, routes, jobs, tests, and middleware, then compares each usage against Gate::define declarations, policy methods, policy mappings, and before/after hooks to report missing or suspicious definitions.
- ▌ Campaign Copywriter · yumaitauStructure, offers, CTAs, and channel patterns for standalone marketing pieces sent or posted to an audience. Use whenever writing, rewriting, or critiquing marketing emails, newsletters, product launch or release announcements, social posts, or ad copy, including subject lines, preview text, and email sequences. Trigger even for small jobs like tightening a subject line or reviewing one LinkedIn post. Reads `.product/` knowledge files from the dot-product skill when present, consumes campaign briefs from marketing-strategist, and pairs with human-copy-style for baseline voice. Not for website page copy with a page-level SEO job, which portfolio-copywriter owns, and not for deciding the campaign's goal, audience, or channels, which marketing-strategist owns.
- ▌ Marketing Strategist · yumaitauCampaign planning and messaging strategy before any copy is written. Use whenever planning a marketing campaign, product launch, or content calendar, choosing which audiences or channels to target, building a messaging framework, or writing a campaign brief. Trigger for asks like "plan the launch", "who should we target", "what should we post this month", "we need a marketing plan", or when someone wants to pressure-test a marketing idea before committing. Reads `.product/` knowledge files from the dot-product skill when present and writes briefs consumed by campaign-copywriter and portfolio-copywriter. Not for writing the copy itself, which those skills own, and not for extracting product knowledge from a codebase, which dot-product owns.
- ▌ Portfolio Copywriter · yumaitauPositioning, structure, proof, and SEO for customer-facing website copy. Use whenever writing, rewriting, expanding, or critiquing copy for a portfolio, marketing, landing, agency, consultancy, or service business site, covering heroes, about pages, service pages, project summaries, case studies, CTAs, headlines, taglines, SEO titles, meta descriptions, and URL slugs. Trigger even for small jobs like shortening a headline or reviewing a single project blurb. Reads `.product/` knowledge files from the dot-product skill when present, and pairs with human-copy-style for baseline voice. Not for marketing emails, newsletters, announcements, social posts, or ad copy, which campaign-copywriter owns, and not for blog posts or UI microcopy with no page-level SEO job, which human-copy-style alone covers.