Results for “a-share”

Share state between Blazor components across render mode boundaries using cascading values, scoped services with change events, or CascadingValueSource via DI.

Create or update standardized object-oriented component documentation by analyzing source code and following a shared template with mode-specific guidance.

Adds smooth, native-feeling animations to React apps using the View Transition API, covering shared elements, route changes, and list reordering with CSS-based control.

This skill should be used when the user asks to "deploy", "upload", "publish", or "pin" any files, folders, frontend projects, or static websites to IPFS. Also activates when user mentions "pinme", "IPFS", or wants to share files via decentralized storage.

Transforms source materials (URLs, PDFs, DOCX, Markdown, text, screenshots) into a single-file HTML web article that is visually polished, offline-accessible, and shareable, using a structured editorial workflow with checkpoints and quality reviews.

Batch-converts UI design screenshots into Vue 3 Composition API components using Vant, Element Plus, or Ant Design Vue, with router wiring and shared component extraction.

Scrapes posts from a Facebook group given a group URL, sort order, and desired count, returning structured post metadata including post_id, permalink, author, timestamp, body text, media, reactions, comments, and shares.

Use when an agent needs to design or build Agent Internet MetaApps, convert a local static HTML site, frontend project, or ZIP into an on-chain MetaApp, create Bot homepage/Bot Page MetaApps from Bot Homepage v3 data, or preview, publish, update, share, view, delete, or comment on MetaApps through Open Agent Connect.

Extract self-contained static HTML from a built web application or React components by inlining CSS and images. Use this skill whenever you need to capture a specific UI state, share a static version of a page, or prepare assets for Stitch upload, even if the user just asks to 'save the HTML' or 'mock the view'.

Create OR review a wireflow — the artifact BETWEEN user journeys and wireframes. It maps whole journeys into swimlane flows with high-level navigation (screens, decisions, system/agent steps) while keeping Jobs-To-Be-Done at the core, WITHOUT deep UI. Use whenever the user wants to "map the flows", "make/build a wireflow", turn journeys / JTBDs / a spec / a live prototype into flows, or put every journey on one board against shared owner lanes — even if they never say "wireflow". ALSO use it to REVIEW or critique an existing wireflow (image, FigJam, or description). In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/wireflow/ with jobs consumed by id from docs/product/jtbd/; pipeline mode derives the method decisions and highlights the riskiest at the gate, standalone mode runs the full grill. CREATE generates verified SVG/HTML (self-checked by rendering and Reading its output) in a horizontal per-journey OR shared-matrix layout, and can rebuild in FigJam. Do

HTML Forms + Sage integration — log1x/sage-html-forms, hf_get_form, addPostObject html-form, Blade form views, x-form.* shared components, hf-validation JS module, hf-success hf-error hf-submitted events, Constraint Validation API, form traps pattern escaping type-tel ValidityState non-enumerable — stateless contact forms with progressive JS validation on top of the HTML Forms WordPress plugin. Invoke for: contact form with HTML Forms plugin, hf_get_form usage, form validation with Constraint API, pattern escaping trap, type=tel Chrome bug, form audit.