ref-sp-js-web-standalone-templatelisted

# Standalone Web App ## Purpose Provide app-level defaults for self-contained browser apps and local web tools that should stay simple, readable, and maintainable without unnecessary framework or build-system overhead. ## When to use this skill - Creating a standalone browser app or local web tool. - Refactoring a no-build web app that is getting too large. - Deciding whether the app can stay framework-free or should escalate to a full React and Next app. - Choosing local assets and browser-loadable libraries for a whole standalone app. ## Scope Boundaries - Use this skill for whole browser-only apps and local web tools you control directly. - Use `ref-sp-js-next-template` when the user explicitly wants a full React and Next app rather than a no-build browser app. - Use `ref-sp-js-react` or `ref-sp-js-next` only after the app has deliberately crossed into those frameworks. - Use `ref-sp-js-userscript` when the code runs inside a userscript manager on someone else's page. - Use `ref-sp-js-javascript` for detailed JavaScript module, JSDoc, and runtime-surface questions once the standalone app model itself is chosen. - Use `ref-sp-dev-projects-architecture` when the question is about repo-wide structure rather than one browser app. ## Defaults - Start with one self-contained HTML file for small and medium apps. - Use semantic HTML before reaching for generic containers. - Prefer no package manager or build pipeline by default. - If Node-based tooling becomes necessary, p