Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

Avinava

@avinava source repo

14 published skills

  1. ▌
    Chart Design · avinava bundle
    Design honest, accessible charts of quantitative data as inline SVG — bar and column charts, line and time series, limit ledgers, distributions, scatter plots, and small multiples. Use when visualizing measured values, choosing a chart type, picking or fixing chart colors, building a categorical palette from design tokens, setting axes and scales, labelling series, or making an existing chart readable in grayscale and in print. Do not use for diagrams of structure or process such as architecture or flows (use diagram-design), for the surrounding report narrative and metric semantics (use analytical-document-design), or for interactive dashboards that require a client-side charting library.
    0
    installs
  2. ▌
    Diagram Design · avinava bundle
    Design editorial-quality diagrams as self-contained inline SVG — architecture diagrams, flows, sequences, state machines, data models, timelines, layer stacks, quadrants, comparisons, and system maps. Use when explaining how a system is arranged, how a process moves, how components depend on each other, or how options compare; when a Mermaid or draw.io diagram needs to be converted into a document's design system; or when an existing diagram looks auto-generated and needs editorial judgment. Do not use for quantitative charts of measured data (use chart-design), for the surrounding report structure (use analytical-document-design), for UI mockups or wireframes, or for producing editable .drawio files.
    0
    installs
  3. ▌
    Writing Documents · avinava bundle
    Write structured technical documents — design-doc, adr, spec, api-contract, architecture, handoff, design-handoff, discovery, test-report, postmortem, proposal, runbook, onboarding, tutorial, how-to, reference, explanation, mulesoft — as Markdown in the repo by default. Use when asked to write or restructure one of those types, including RFCs, ADRs, developer handoffs, API writeups, test summaries, discovery briefs, or MuleSoft project docs. Produce designed HTML or PDF only when asked. Do not use for casual edits to existing markdown, metric-led reports (analytical-document-design), slides (presentation-design), standalone charts or diagrams, restyling a file into HTML unprompted, or Mule markdown refresh when mule-docs is installed.
    0
    installs
  4. ▌
    Brand Theme Design · avinava bundle
    Turn a brand into a working theme for this design system — from a screenshot, a website, a PDF brand guide, a style guide, or a handful of hex values. Use when asked to match a company's brand, apply brand colors or brand guidelines to documents, make reports look like an existing site or product, build a theme from a logo or screenshot, or fill in the brand-template slot; and when an existing theme needs its contrast, accent, or print behavior audited. Do not use for choosing between the themes that already ship (that is a one-line answer in core/tokens.md), for restyling a single document rather than creating a reusable theme, or for general visual design of a report, diagram, chart, or deck — those belong to the skill for that artifact.
    0
    installs
  5. ▌
    Presentation Design · avinava bundle
    Design presentation decks as self-contained 16:9 HTML slides that export cleanly to PDF — board updates, project reviews, findings readouts, proposals, and conference talks. Use when building a deck, slides, a presentation, or a leadership readout; when converting a report or a set of findings into slides; or when an existing deck needs a coherent visual system and a clean PDF export. Do not use for documents meant to be read rather than presented (use analytical-document-design or writing-documents), for a single standalone chart or diagram, or when the user specifically needs an editable .pptx file.
    0
    installs
  6. ▌
    Analytical Document Design · avinava bundle
    Design evidence-led analytical documents from structured data — executive reports, portfolio reviews, operational audits, inventory analyses, compliance summaries, metric dashboards, and standalone self-contained HTML reports. Use when turning a CSV, inventory, export, or metric set into a professional document; when asked to show where usage, cost, or risk is concentrated; when a report needs clear metric semantics, reconciled totals, accessible charts, and clean print/PDF output; or when an existing dashboard needs to be made defensible rather than merely decorated. Do not use for a single standalone chart (use chart-design), a slide deck (use presentation-design), a prose-first document such as an RFC or spec (use writing-documents), an application UI, or a transactional product dashboard.
    0
    installs
  7. ▌
    Mule Ops · avinava bundle
    Analyze MuleSoft runtime health across one or more applications using Anypoint logs, metrics, deployment state, and cross-system correlation. Use for production or non-production health checks, incident windows, error spikes, latency or memory investigations, deployment-impact checks, and recurring operational reviews. Use the available Anypoint connector when configured, or apply the same evidence workflow to exported telemetry. Do not use for source-code changes unless the user also requests a fix.
    0
    installs
  8. ▌
    Mule Docs · avinava bundle
    Analyze MuleSoft Mule 4 repositories and create or update evidence-backed Markdown documentation with Mermaid diagrams. Use for project overviews, architecture and flow documentation, API contracts, connector and DataWeave documentation, configuration guides, onboarding, deployment, operations, testing, troubleshooting, or documentation-gap audits. Use for full-project documentation and targeted refreshes after Mule XML, RAML/OAS, DataWeave, MUnit, configuration, or deployment changes. Do not use for generic non-Mule repositories or source-code changes unrelated to documentation.
    0
    installs
  9. ▌
    Mule Build · avinava bundle
    Validate, test, package, and locally run a MuleSoft Mule 4 application using its established repository commands and configured build tools, and prepare versions, commits, and tags only when explicitly requested. Use for local build validation, static analysis, MUnit execution, deployable artifacts, local runtime work, and versioned release preparation. Do not use for Exchange publishing or Anypoint deployment; route those authorized platform actions to mule-ops and the Anypoint connector. Default to validate-and-package; treat versioning, local runtime changes, commits, tags, pushing, and skipping tests as explicit choices.
    0
    installs
  10. ▌
    Mule Review · avinava bundle
    Review MuleSoft Mule 4 working changes, commit ranges, branches, pull requests, whole repositories, or release readiness and return prioritized evidence-backed findings with remediation options. Use for code review, PR review, project health audits, architecture and contract consistency checks, incident-prevention reviews, and pre-release gates covering Mule XML, RAML/OAS, DataWeave, connectors, configuration, MUnit, deployment, operations, security, privacy, and documentation. Review and report by default; do not modify source, post comments, approve changes, or perform release actions unless the user explicitly requests them.
    0
    installs
  11. ▌
    Mule Testing · avinava bundle
    Create, repair, and refactor behavior-focused MUnit tests for MuleSoft Mule 4 applications, including event setup, fixtures, mocks, spies, assertions, error expectations, and test-only build configuration. Use when adding missing MUnit coverage, diagnosing or fixing a failing MUnit test, preserving behavior during a Mule change, or improving test fidelity. Route production Mule source changes to mule-development and execution-only, packaging, or release work to mule-build.
    0
    installs
  12. ▌
    Mule API Design · avinava bundle
    Design, author, revise, or assess consumer-facing MuleSoft HTTP API contracts in RAML 1.0 or OpenAPI 3.0 using explicit resource, method, URI, data, error, security, compatibility, and governance decisions. Use for API design workshops, URL and naming guidance, new RAML/OAS contracts, contract-first changes, and contract-only reviews. Maintain RAML 0.8 or OAS 2.0 when required, but do not use for AsyncAPI, event schemas, Mule implementation, MUnit authoring, or general project review.
    0
    installs
  13. ▌
    Mule Development · avinava bundle
    Create or modify MuleSoft Mule 4 production flows, DataWeave, APIKit routing, error handling, connectors, queues, batch jobs, and configuration using evidence-based project conventions and post-change validation. Use when implementing Mule application behavior or aligning implementation to an existing contract. Route HTTP API design and RAML/OAS contract authoring to mule-api-design, MUnit authoring and repair to mule-testing, and review-only work to mule-review.
    0
    installs
  14. ▌
    Mule Troubleshooting · avinava bundle
    Diagnose MuleSoft incidents and produce evidence-backed root-cause assessments or fix plans for timeouts, connection failures, rate limits, concurrency, batch processing, queues, deployment transitions, memory pressure, and cross-application error propagation. Use when a Mule runtime symptom must be traced through code, configuration, logs, metrics, and dependencies. Diagnose by default; modify source or configuration only when the user explicitly requests implementation.
    0
    installs