mambisi

Use when turning a Claude Design (or any mockup/design) into a well-structured pocopine app — choosing app architecture (a store plus layout/leaf components), translating inline styles into Pine Stylekit, wiring icons and resizable regions, and verifying the result.

Use when working with the pocopine Pine icons feature — the `icon!` proc macro for compile-time Rust SVG embedding, or the `<pine-icon>` template primitive with `register_icons!` for tree-shaking-friendly template rendering.

Use when building styles with Pine Stylekit, the Pocopine-native utility-CSS compiler, or working with @theme tokens and CSS generation in Rust/WASM projects

Use when building enter/leave transitions, layout animations, stagger effects, or spring-physics motion in pocopine components

Use when implementing authentication in pocopine apps — JWT verification, credentials, OAuth providers, session management, or guards

Use when defining background jobs, enqueueing work, configuring workers, or troubleshooting job execution in pocopine apps

Use when setting up or working with Pocopine's managed .client.ts modules for importing npm SDKs (Firebase, analytics, etc.) with typed Rust facades

Use when deploying a pocopine full-stack or static app to Fly.io, Railway, Render, or other hosts using the RFC 080 deploy contract

Use whenever you are about to run, serve, preview, or build a pocopine application or example (anything with a wasm client + a server bin, or a `[package.metadata.pocopine]` block) — including writing the run instructions in a README. ALWAYS drive it through the pocopine CLI (`pocopine run` / `pocopine dev` / `pocopine build`), never a hand-rolled `wasm-pack build` followed by `cargo run --bin`. Covers the subcommands + flags, what the CLI does that manual steps silently miss, and the contract a runnable crate must satisfy.

Use when authoring or touching Pocopine Agenkit AI work — flows, the #[ai_flow] / #[ai_tool] macros, AiAgent / AiRetriever, ctx.ai / ctx.step / ctx.parallel / ctx.reduce / ctx.retrieve / ctx.agent, agent threads, the streaming route, or exposing a flow through a #[server] fn. Keeps work on the traceable, principal-scoped path the runtime is designed around (RFC-093) and off the easy-but-wrong path (hidden DB/file reads, undeclared resources, secrets in trace/stream fields).

Use when creating or restructuring a pocopine library crate that has host-only and/or wasm-only code (anything depending on axum/tokio for the server, or wasm-bindgen/web-sys for the browser). Put platform code in `server` and/or `client` modules gated ONCE at the crate root, instead of sprinkling `#[cfg(target_arch = "wasm32")]` on every item and every `pub use`. Covers the lib.rs gating pattern, when to use a `server.rs` file vs a `server/` folder, sibling-import paths, and the Cargo.toml target tables.

Use when adding or touching any hashing, checksums, base64, percent-encoding / URL escaping, or request signing (HMAC, Azure Shared-Key / SAS, token hashing) in the pocopine workspace. Routes the work through the shared pocopine-crypto and pocopine-codec crates instead of pulling in sha2 / md-5 / crc32c / hmac / base64 / percent-encoding directly or hand-rolling encoders.