Back to search
fstack
MarketplaceWorks with Claude CodeGitHub
Claude Code skills for indie founders shipping B2C apps: engineering judgment, design, copy, onboarding, paywalls and win-back.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/fabiojonathanarifin--fstack)HTML
<a href="/listings/fabiojonathanarifin--fstack"><img src="/api/listings/fabiojonathanarifin--fstack/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
/plugin marketplace add fabiojonathanarifin/fstack /plugin install fstack@fstack /plugin install fstack-mobile@fstack
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 23 lines
- {
- "name": "fstack",
- "owner": {
- "name": "Fabio Jonathan Arifin",
- "url": "https://github.com/fabiojonathanarifin"
- },
- "metadata": {
- "description": "Skills for indie founders: a product-agnostic core and a B2C mobile pack.",
- "version": "0.2.0"
- },
- "plugins": [
- {
- "name": "fstack",
- "description": "Engineering judgment, premium design and copy that doesn't read as AI. Product-agnostic skills for any codebase, plus /in-your-own-words.",
- "source": "./plugins/fstack"
- },
- {
- "name": "fstack-mobile",
- "description": "Playbooks that make a B2C mobile app earn money: onboarding, paywall, review-prompt timing, premium gating, cancellation win-back, and Expo / React Native gotchas.",
- "source": "./plugins/fstack-mobile"
- }
- ]
- }
README.md · README · 65 lines
- # fstack
- Skills for Claude Code from a solo founder shipping B2C apps. Built while running EchoForge, maker of Protos, Airlophone and ReadersGuild. Each rule came from a real launch, a rejection, or a bug that cost a day.
- ## What's inside
- Two plugins. Install one or both.
- **`fstack`**: works in any codebase.
- | Skill | Loads when you are |
- |---|---|
- | `engineering-principles` | planning, debugging, refactoring or reviewing code |
- | `design-standards` | designing any screen, flow or interaction |
- | `copywriting-rules` | writing anything a user reads |
- | `/in-your-own-words` | typing it, to check the agent understood your goal |
- **`fstack-mobile`**: for B2C mobile apps.
- | Skill | Loads when you are |
- |---|---|
- | `mobile-onboarding-paywall` | building onboarding, a paywall, or a review prompt |
- | `in-app-premium-gating` | adding a locked feature or upgrade prompt |
- | `subscription-winback` | building a cancel flow or retention offer |
- | `expo-react-native` | working in an Expo or React Native app |
- Rules load themselves when the task calls for them. Checks wait for you to type them.
- ## Install
- ```
- /plugin marketplace add fabiojonathanarifin/fstack
- /plugin install fstack@fstack
- /plugin install fstack-mobile@fstack
- ```
- ## A few rules worth knowing
- - Apple rejects apps that ask for a rating during onboarding (guideline 5.6.3). Ask after the first real win, at least 8 hours after install.
- - RevenueCat checks entitlements by the entitlement ID, not the product ID. A mismatch makes every purchase succeed while access stays locked.
- - When two fixes built on the same assumption both fail, test the assumption before writing a third.
- - A win-back offer should be a StoreKit promotional offer, not a cheaper public product that undercuts full-price sales.
- ## Optional: always-on rules
- Skills load on demand. If you want the core principles in every session, paste this into your `CLAUDE.md`:
- ```markdown
- - Design for the scale the product implies, not the toy example in front of you.
- - Touch only what the task needs. Don't tidy nearby code on the way past.
- - Define the check before coding, and show its output when reporting done.
- - When two fixes that share one assumption fail, write the assumption down and test it before a third fix.
- - Before trusting a number, name what limits it and rule out that it measured something else.
- - Fix where the system first went wrong. A guard on a state that should never exist hides the bug.
- - No em dashes, en dashes or ellipses in user-facing copy.
- - Never use a sparkles icon.
- ```
- ## Credits
- Several engineering principles are adapted from [pstack](https://github.com/cursor/plugins/tree/main/pstack). The `copywriting-rules` skill works best alongside [humanizer](https://github.com/blader/humanizer).
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.