featuredrop-setup
/featuredrop-setup
Configure FeatureDrop product adoption toolkit in any project. Use when adding changelogs, feature badges, onboarding tours, checklists, hotspots, feedback widgets, or surveys to an application.
- Author
- glincker ↗
- Repository
- featuredrop ↗
- Licence
- MIT
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Configure FeatureDrop product adoption toolkit in any project. Use when adding changelogs, feature badges, onboarding tours, checklists, hotspots, feedback widgets, or surveys to an application.
Original author description
Configure FeatureDrop product adoption toolkit in any project. Use when adding changelogs, feature badges, onboarding tours, checklists, hotspots, feedback widgets, or surveys to an application.
How it works
- Setup Pattern
- Imports (ALWAYS use subpath imports)
- Hooks (prefer these for custom UI / shadcn projects)
- Components (ready-made UI)
- Feature Manifest Format
- Storage Adapters
- Provider Props
- Tailwind Integration
- Rules
SKILL.md preview
---
name: featuredrop-setup
description: >
Configure FeatureDrop product adoption toolkit in any project. Use when adding
changelogs, feature badges, onboarding tours, checklists, hotspots, feedback
widgets, or surveys to an application.
---
# FeatureDrop — Product Adoption Toolkit
Open-source, zero-dependency library for in-app feature discovery. < 3 kB core.
## Setup Pattern
1. `npm install featuredrop`
2. Create a JSON manifest: `[{ id, label, description, releasedAt, showNewUntil? }]`
3. Wrap root: `<FeatureDropProvider manifest={features} storage={new LocalStorageAdapter()}>`
4. Add components or use headless hooks.
## Imports (ALWAYS use subpath imports)
```ts
// Core (no React, no UI)
import { isNew, getNewFeatures, createManifest, LocalStorageAdapter } from 'featuredrop'
// React components (ready-made UI)
import { NewBadge, ChangelogWidget, Tour, Checklist, Banner, Toast } from 'featuredrop/react'
// Headless hooks (data + actions, no JSX — for custom design systems / shadcn)
import { useChangelog, useNewFeature, useNewCount, useTour, useChecklist } from 'featuredrop/react/hooks'
// Storage adapters
import { PostgresAdapter, RedisAdapter, IndexedDBAdapter, HybridAdapter } from 'featuredrop/adapters'
// Validation
import { validateManifest } from 'featuredrop/schema'
// Testing helpers
import { createMockManifest, createMockStorage, TestProvider } from 'featuredrop/testing'
// Tailwind plugin
import { featureDropPlugin } from 'featuredrop/tailwind'
```
## Hooks (prefer these for custom UI / shadcn projects)
| Hook | Returns |
|------|---------|
| `useNewFeature(id)` | `{ isNew, feature, dismiss }` |
| `useNewCount()` | `number` — unread badge count |
| `useChangelog()` | `{ features, newFeatures, newCount, dismiss, dismissAll, markAllSeen, getByCategory }` |
| `useTour(id)` | `{ currentStep, stepIndex, totalSteps, isActive, start, next, prev, skip, complete, goTo }` |
| `useChecklist(id)` | `{ tasks, completedCount, totalCount, progress, isComplete, completeTask, resetTask }` |
| `useSurvey(id)` | `{ isVisible, questions, submit, askLater, dismiss }` |
| `useFeatureDrop()` | Full provider context (features, count, dismiss, throttle controls, engine) |
| `useTabNotification()` | Browser tab title: `"(3) My App"` |
## Components (ready-made UI)
NewBadge, ChangelogWidget, ChangelogPage, Tour, Checklist, Spotlight, SpotlightChain,
Hotspot, TooltipGroup, Banner, Toast, AnnouncementModal, Survey, FeedbackWidget,
FeatureRequestButton, FeatureRequestForm
## Feature Manifest Format
```ts
{
id: string // unique identifier
label: string // display title
description: string // what changed
releasedAt: string // ISO date
showNewUntil?: string // ISO date — auto-expire badge
category?: string // group: "ui", "api", "billing"
type?: string // "feature" | "improvement" | "fix" | "deprecation"
priority?: string // "low" | "medium" | "high" | "critical"
cta?: { label: string; url: string }
audience?: Record<string, string[]> // user segmentation
}
```
## Storage Adapters
Default: `LocalStorageAdapter` (browser). Server: `PostgresAdapter`, `RedisAdapter`.
Offline: `IndexedDBAdapter`. Hybrid: `HybridAdapter` (local + remote sync).
Custom: implement `{ getWatermark, setWatermark, getDismissedIds, addDismissedId }`.
## Provider Props
```tsx
<FeatureDropProvider
manifest={features} // required
storage={adapter} // required
analytics={{ onFeatureSeen, onFeatureDismissed, onFeatureClicked }}
userContext={{ plan, role, region }} // for audience targeting
appVersion="2.1.0" // semver gating
throttle={{ maxToastsPerSession: 3, modalCooldownMs: 120_000 }}
locale="en" // i18n (en/es/fr/de/pt/zh-cn/ja/ko/ar/hi)
animation="normal" // "none" | "subtle" | "normal" | "playful"
engine={engineInstance} // optional: FeatureDropEngine for smart delivery
/>
```
## Tailwind Integration
```ts
// tailwind.config.ts
import { featureDropPlugin } from 'featuredrop/tailwind'
export default {
plugins: [featureDropPlugin({ prefix: 'fd' })],
}
// Adds: fd-badge, fd-badge-dot, fd-badge-count, fd-animate-pulse, fd-animate-fade-in
// CSS vars: --fd-new, --fd-changelog-bg, --fd-tour-bg (auto dark mode)
```
## Rules
- Always use subpath imports (`featuredrop/react`, not just `featuredrop`)
- Prefer hooks from `featuredrop/react/hooks` when the project uses shadcn, Radix, or custom design system
- Features auto-expire via `showNewUntil` — don't build manual expiry logic
- Zero production dependencies — don't add external deps
- TypeScript strict mode — no `any` types
- All components support headless mode via render props
- Core < 3 kB, React ~12 kB, fully tree-shakeable
Versions
The database has no other skills named featuredrop-setup.
Database snapshot: 13.11.2026 · package version f770c9168bf6 (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
- 100product-tour-onboarding-ui-stinger
Build in-app tours and onboarding UI. Use for tour tools, tooltips, checklists, segment triggers, or maintenance after UI changes. Read README.md for the guide map. - 85atlas
Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports. Use when asked to "write an ADR", "map the architecture", "document this decision", "onboarding docs", or "what changed". - 100create-code-tours
Create CodeTour .tours/*.tour files for onboarding to a software domain or bounded context, explaining Git changes through cause and effect, or walking business logic in complete control-flow blocks. Use for navigable source-code tours. - 100melonhelp-feedback
Integrate Melonhelp Feedback into a web app and fix what its users report: feedback button and public portal, satisfaction surveys, identified users, error reporting and the team's agent queue. Use when the user asks to install, add, configure, verify or debug Melonhelp…