一键导入
faq
Use when adding, editing, or removing StakTrakr in-app FAQ entries in the Settings FAQ tab, including known or honest limitation copy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when adding, editing, or removing StakTrakr in-app FAQ entries in the Settings FAQ tab, including known or honest limitation copy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when starting a new patch session and needing to pick a Plane issue to work on before claiming a version lock and creating a worktree.
Use when starting a new patch session and needing to pick a Plane issue to work on before claiming a version lock and creating a worktree.
Post-deploy verification for both Portainer (home) and Fly.io (cloud) environments. Runs environment-appropriate health checks, log inspection, env var verification, cron validation, and endpoint smoke tests. Covers the gap between "deploy succeeded" and "deploy actually works." Triggers on: "deploy verify", "post-deploy", "verify deploy", "smoke test deploy", "did the deploy work", "check the deploy", "/deploy-verify"
StakTrakr-specific Phase 1 version bump — edits 6 files, trims What's New, delegates sw.js to pre-commit hook.
API feeds, pollers, feed thresholds, data paths, StakTrakrApi structure, Fly.io and health badge issues.
Ship dev→main — PR, resolve threads, GitHub Release. Only on explicit user "ready to ship".
| name | faq |
| description | Use when adding, editing, or removing StakTrakr in-app FAQ entries in the Settings FAQ tab, including known or honest limitation copy. |
Update the in-app FAQ in Settings > FAQ. Use when adding, editing, or removing FAQ entries. Triggers on: "faq", "add faq", "update faq", "faq entry", "known limitation", "honest limitation".
Single source: index.html inside #settingsPanel_faq (Settings modal > FAQ tab).
There is NO external FAQ file, no GitHub wiki FAQ, no dynamically loaded FAQ. It's all static HTML in index.html. The README references it but doesn't duplicate it.
Access path: faq.js is a shim that redirects showFaqModal() to showSettingsModal('faq').
The FAQ is organized into collapsible sections using <details> + <summary> elements:
<!-- Section wrapper -->
<div class="settings-fieldset">
<div class="settings-fieldset-title">EMOJI Section Name</div>
<details class="faq-item">
<summary class="faq-question">Question text here</summary>
<div class="faq-answer">
<p>Answer paragraph(s) here.</p>
</div>
</details>
<!-- More faq-item entries... -->
</div>
| # | Title | Line Range | Content |
|---|---|---|---|
| 1 | Your Data & Privacy | ~3818 | Who sees data, cookies, tracking, browser history, malware |
| 2 | Backups & Export | ~3895 | Data export, future-proofing, developer abandonment |
| 3 | Cloud Storage | ~3930 | Dropbox visibility, encryption explanation |
| 4 | Security | ~3955 | Hacker protection, security practices |
| 5 | About the App | ~3974 | Differentiators, cost/subscriptions |
| 6 | Honest Limitations | ~4010 | localStorage clearing, file:// protocol, no audit, single cloud provider, spot prices, Numista dimensions |
| 7 | More Information | ~4067 | Resource links (Privacy Policy, Source Code, Community, Changelog) |
Note: Line numbers shift as the file grows. Search for the section title text to find the right location.
index.html</div> of that section's settings-fieldset:<details class="faq-item">
<summary class="faq-question">Your question here</summary>
<div class="faq-answer">
<p>
Your answer here. Use <strong>bold</strong> for emphasis, <code>code</code> for technical
terms.
</p>
<p>Second paragraph if needed.</p>
</div>
</details>
— for em dashes, & for ampersands — standard HTML entities<summary><p> tags, can include <ul>, <strong>, <code>, <a> links<details class="faq-technical"> inside the answerA second FAQ panel exists inside the Cloud Sync modal at #settingsPanel_cloud (lines ~4986-5065). This covers cloud-specific questions:
Same HTML pattern (faq-item / faq-question / faq-answer), just located in a different modal section.
faq.js — it's just a redirect shim