Skip to content
Skills Library
Programming · Building & coding

platform-engineering

/platform-engineering

Platform mechanisms and compatibility for browser, PWA, mobile, Electron and Tauri applications. TRIGGER WHEN: building or reviewing supported browsers/devices, native integration, offline lifecycle, packaging, or platform-specific trust boundaries.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
16
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Platform mechanisms and compatibility for browser, PWA, mobile, Electron and Tauri applications. TRIGGER WHEN: building or reviewing supported browsers/devices, native integration, offline lifecycle, packaging, or platform-specific trust boundaries.

Original author description

Platform mechanisms and compatibility for browser, PWA, mobile, Electron and Tauri applications. TRIGGER WHEN: building or reviewing supported browsers/devices, native integration, offline lifecycle, packaging, or platform-specific trust boundaries.

How it works

  1. Load references on demand
Original SKILL.md headings · 112 lines, 986 words
SKILL.md preview
---
name: platform-engineering
description: >
  Platform mechanisms and compatibility for browser, PWA, mobile, Electron and Tauri applications.
  TRIGGER WHEN: building or reviewing supported browsers/devices, native integration, offline lifecycle, packaging, or platform-specific trust boundaries.
---

<daodan_host_binding host="pi">
This binding governs execution of this package and its loaded references. It takes
precedence over executable examples written for another host. Use only registered
tools and their actual input schema; an example never creates a tool, argument,
permission, model alias or nested worker capability. Preserve the generated worker
allowlist, dependency closure, scope and delivery contracts.

Pi binding: repository reads use read/find/grep, writes use edit/write, and shell
execution uses bash or the registered powershell alternative. Use their actual
command, timeout and process-control schema rather than capitalized foreign tools.
Core Pi supplies neither subagent nor MCP. Isolated workers require pi-subagents:
pi install npm:pi-subagents. Use that extension's registered subagent schema and
pass the full rendered role body inline. Role skills named <plugin>-<role> are
body resources with automatic invocation disabled, not a built-in named agent.
Workflow prompt entries use /<plugin>-<workflow>; ordinary skills use their exact
registered names. If isolation is mandatory and unavailable, stop the phase.
MCP requires pi-mcp-adapter: pi install npm:pi-mcp-adapter, then register the
generated server command in its supported MCP configuration.
Keep the selected package's full local dependency closure. Provision qualified
foreign providers as skills/resources this runtime can load; Pi does not install
another host's marketplace plugin from a Claude install command.
Inherit the active session's model and default variant. A source model alias such
as sonnet is not a portable override; request a different model only through an
explicit adapter mapping to a valid host identity and user authorization.
Kernel <owner>:<skill> references identify the logical provider. Ordinary Pi
skills retain their source frontmatter name, so resolve the actual registered name
and provider path from the active inventory; do not invent a prefixed native ID.

The executing agent and its coordinator own continuation, recovery, verification
and delivery. Skills supply knowledge and method instructions; they are not
executors or a runtime persistence mechanism.

Resolve each component by kind and exact installed identity. A role is dispatched
as a worker, a skill loads instructions, and a workflow starts its declared method.
Kernel owner-qualified skill references are logical provider identities: resolve
them to the actual host registry name and verified installed provider path. Do not
invent a registry string by adding an owner's prefix when the host does not use it.
Do not load an agent identity as a skill or execute a workflow name as a shell
command. Declared required foreign providers remain mandatory. If a required
provider or capability (including required MCP access or isolation) is unavailable,
stop its dependent phase and report the missing capability. Optional external
providers follow the method's declared selection and absence behavior; their
absence alone does not block the base workflow. Report any explicitly requested
but unavailable provider contribution as unfulfilled and continue independent
work. Do not install a different host's plugin or
substitute unrelated skills to claim coverage.

Shell execution alone does not establish interactive stdin. Before a capture or
checkpoint, use an available session-control mechanism. When stdin is unavailable,
keep user-driven capture in a supported background process with bounded output and
an explicit stop signal controlled by the coordinator after the user's completion
message. Close owned browser/process resources on completion or cancellation.

Continue working within the current authorization while the requested result is
achievable. After a tool error, inspect its cause, correct the relevant input or
implementation, retry when justified and verify the outcome; never repeat a
failing action blindly. Do not close the turn with a promise or a partial result
when an authorized next step can still produce or verify the requested result.
Stop only for a documented real impediment, a missing required capability, an
unresolved human decision or the caller's stop request. At that boundary, report
completed results, remaining work and the concrete prerequisite for continuation;
continue any independent work that the blocker does not prevent.

A tool's successful exit, a worker stop or an idle session is not the deliverable.
Return final text naming observed findings, artifact paths, executed checks and
blockers. An empty worker result is missing delivery: inspect or resume that worker
when permitted, or record failure. Verify required artifacts and candidate gates
before marking the requested outcome complete.

This is an execution binding, not a rewrite of source examples. Preserve programming
language fences, domain code and host APIs that are the subject of marketplace-ops
or agent-sdk-builder. A host-as-subject API is not a tool provided to this session.
Compiled binding and static checks do not prove an installed host executed a run.
</daodan_host_binding>

# Platform engineering

Bind advice to the application's declared target platforms, versions, distribution
and required behavior. Read relevant source and effective configuration before
applying a rule. Historical reference examples, numeric budgets and preferred
technologies are leads; verify applicable version behavior and requirements before
treating them as obligations. Missing measurements remain unknown.

The autonomous `platform-reviewer` checks client platform compatibility and
mechanisms. It reports adjacent security, generic performance or backend
operability leads to the caller for routing through the existing review process.
It does not claim those separate dimensions were reviewed.

## Load references on demand

Choose only sections needed for the actual mechanism:

| Mechanism | References inside this skill |
|---|---|
| Browser/native identity and credential boundary | `auth-tokens.md`, `passkeys-webauthn.md`, `platform-security.md` |
| Browser execution and content boundaries | `xss-csp.md`, `server-validation.md`, `api-security.md`, `secrets-management.md` |
| Client/server and transport design | `client-server-architecture.md`, `api-design.md` |
| Offline synchronization and caches | `offline-first.md` |
| Platform delivery and configuration | `infrastructure.md`, `platform-security.md` |
| Platform-specific rendering, power and resource constraints | `frontend-performance.md`, `backend-and-platform-performance.md` |

References never grant execution or mutation. Audit is read-only and does not
run a profiling query, launch a device or exercise an application without the
caller's corresponding authorization. State verified target/version, mechanism,
requirement, counterevidence and coverage in findings; neither a checklist item
nor a preferred package establishes a defect.

For the targeted platform audit under `/daodan:check-health`, read
`references/audit.md`. Inside a senior-review run, use the prepared brief and
dispatch this plugin's reviewer once; do not start the standalone audit as well.
Files in this package (16)
  • SKILL.md 7 KB
  • SKILL.toml 1 KB
  • references/api-design.md 9 KB
  • references/api-security.md 8 KB
  • references/audit.md 8 KB
  • references/auth-tokens.md 8 KB
  • references/backend-and-platform-performance.md 12 KB
  • references/client-server-architecture.md 6 KB
  • references/frontend-performance.md 11 KB
  • references/infrastructure.md 10 KB
  • references/offline-first.md 8 KB
  • references/passkeys-webauthn.md 11 KB
  • references/platform-security.md 14 KB
  • references/secrets-management.md 7 KB
  • references/server-validation.md 7 KB
  • references/xss-csp.md 8 KB

Versions

RepositoryScoreLicence
This page · acaprino/alfio-claude-plugins95MIT
magnus919/agent-skills100MIT
acaprino/alfio-claude-plugins95MIT
acaprino/alfio-claude-plugins95MIT
acaprino/alfio-claude-plugins95MIT
acaprino/alfio-claude-plugins95MIT
acaprino/alfio-claude-plugins95MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 7c16039e816e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100electron
    Electron framework for building cross-platform desktop applications with JavaScript, HTML, and CSS. Covers architecture, IPC, security, packaging, auto-updates, and backend integration patterns. USE WHEN: user mentions "Electron", "desktop app", "cross-platform application",…
  • 100platform
    Platform surfaces — mobile/PWA, desktop, React Native, i18n, SEO/metadata, payments, transactional email, AI chat UI. Use when the work targets a platform surface rather than a generic component — mobile and PWA patterns, desktop and Electron/Tauri conventions, React…
  • 100pwa-development
    Progressive Web App architecture, service workers, offline storage, Web Push and cross-engine compatibility. TRIGGER WHEN: building or auditing PWAs: Web App Manifest, service workers, Workbox, Serwist, vite-plugin-pwa, Web Push/VAPID, OPFS, Background Sync, Project Fugu, TWA or…
  • 100pwa-development
    Progressive Web App architecture, service workers, offline storage, Web Push and cross-engine compatibility. TRIGGER WHEN: building or auditing PWAs: Web App Manifest, service workers, Workbox, Serwist, vite-plugin-pwa, Web Push/VAPID, OPFS, Background Sync, Project Fugu, TWA or…
  • 100pwa-stinger
    Implement browser PWA manifest, service-worker lifecycle and bounded public offline assets. Use for scoped PWA/offline changes. Read README.md for the guide map.
  • 90mobile-engineering
    Design, implement, test, and release cross-platform or native mobile applications, including Flutter and React Native. Use for mobile UI, app lifecycle, offline behavior, navigation, permissions, push notifications, performance, and store readiness.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.