Skip to content
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
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/fabiojonathanarifin--fstack/badge.svg)](/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
  1. {
  2. "name": "fstack",
  3. "owner": {
  4. "name": "Fabio Jonathan Arifin",
  5. "url": "https://github.com/fabiojonathanarifin"
  6. },
  7. "metadata": {
  8. "description": "Skills for indie founders: a product-agnostic core and a B2C mobile pack.",
  9. "version": "0.2.0"
  10. },
  11. "plugins": [
  12. {
  13. "name": "fstack",
  14. "description": "Engineering judgment, premium design and copy that doesn't read as AI. Product-agnostic skills for any codebase, plus /in-your-own-words.",
  15. "source": "./plugins/fstack"
  16. },
  17. {
  18. "name": "fstack-mobile",
  19. "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.",
  20. "source": "./plugins/fstack-mobile"
  21. }
  22. ]
  23. }
README.md · README · 65 lines
  1. # fstack
  2. 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.
  3. ## What's inside
  4. Two plugins. Install one or both.
  5. **`fstack`**: works in any codebase.
  6. | Skill | Loads when you are |
  7. |---|---|
  8. | `engineering-principles` | planning, debugging, refactoring or reviewing code |
  9. | `design-standards` | designing any screen, flow or interaction |
  10. | `copywriting-rules` | writing anything a user reads |
  11. | `/in-your-own-words` | typing it, to check the agent understood your goal |
  12. **`fstack-mobile`**: for B2C mobile apps.
  13. | Skill | Loads when you are |
  14. |---|---|
  15. | `mobile-onboarding-paywall` | building onboarding, a paywall, or a review prompt |
  16. | `in-app-premium-gating` | adding a locked feature or upgrade prompt |
  17. | `subscription-winback` | building a cancel flow or retention offer |
  18. | `expo-react-native` | working in an Expo or React Native app |
  19. Rules load themselves when the task calls for them. Checks wait for you to type them.
  20. ## Install
  21. ```
  22. /plugin marketplace add fabiojonathanarifin/fstack
  23. /plugin install fstack@fstack
  24. /plugin install fstack-mobile@fstack
  25. ```
  26. ## A few rules worth knowing
  27. - 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.
  28. - RevenueCat checks entitlements by the entitlement ID, not the product ID. A mismatch makes every purchase succeed while access stays locked.
  29. - When two fixes built on the same assumption both fail, test the assumption before writing a third.
  30. - A win-back offer should be a StoreKit promotional offer, not a cheaper public product that undercuts full-price sales.
  31. ## Optional: always-on rules
  32. Skills load on demand. If you want the core principles in every session, paste this into your `CLAUDE.md`:
  33. ```markdown
  34. - Design for the scale the product implies, not the toy example in front of you.
  35. - Touch only what the task needs. Don't tidy nearby code on the way past.
  36. - Define the check before coding, and show its output when reporting done.
  37. - When two fixes that share one assumption fail, write the assumption down and test it before a third fix.
  38. - Before trusting a number, name what limits it and rule out that it measured something else.
  39. - Fix where the system first went wrong. A guard on a state that should never exist hides the bug.
  40. - No em dashes, en dashes or ellipses in user-facing copy.
  41. - Never use a sparkles icon.
  42. ```
  43. ## Credits
  44. 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).
  45. ## License
  46. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.