flpbalada
- 123 skills
- 0 followers
- 24 repo stars
- 6 days ago last updated
- ▌ To Prd · flpbalada bundleConvert a discussion into a concise PRD covering users, the problem, requirements, technical implementation, and constraints. Use when the user asks to turn a discussion into a PRD.
- ▌ Discuss Task · flpbalada bundleBuild shared understanding before action by interviewing the user about ambiguous implementation, product, planning, or design tasks. Use when goal, scope, constraints, risks, edge cases, success criteria, done state, or next action are unclear; when user wants a thinking partner; or when user needs a handoff-ready task prompt. Use to-prd for a full PRD or to-spec for a short specification.
- ▌ To Spec · flpbalada bundleWrite a short spec in ASD-STE100 Simplified Technical English with users, problem, requirements, and open questions. Use for tasks or discussions with open requirements.
- ▌
- ▌ Weekly Project Update · flpbalada bundleAsk the user for project status, then draft an English weekly update and suggested Health value using the Vilgain project wiki format.
- ▌ Making Product Decisions 2 · flpbaladaFramework for structured product decision-making. Use when facing complex tradeoffs, aligning stakeholders, documenting decisions, or choosing between multiple valid approaches.
- ▌ Visual Cues Cta Psychology 2 · flpbaladaDesign effective CTAs using visual attention and gaze psychology principles. Use when designing landing pages, button hierarchies, conversion elements, or optimizing user attention flow through interfaces.
- ▌ Cognitive Fluency Psychology 2 · flpbaladaApply cognitive fluency principles to improve clarity, trust, and conversion. Use when designing landing pages, writing copy, creating interfaces, or optimizing any content for better user comprehension and engagement.
- ▌ What Not To Do As Product Manager 2 · flpbaladaAnti-patterns and mistakes to avoid as a product manager. Use when evaluating leadership behaviors, improving team dynamics, reflecting on management practices, or onboarding new product managers.
- ▌ Kanban 2 · flpbaladaVisualize and optimize workflow with Kanban boards. Use when managing team work, identifying bottlenecks, improving delivery flow, or implementing continuous improvement in product development.
- ▌ Five Whys 2 · flpbaladaConduct root cause analysis using the Five Whys technique. Use when investigating problems, debugging issues, understanding failures, analyzing churn, or finding the underlying cause of any issue.
- ▌ Hicks Law 2 · flpbaladaOptimize decision-making speed by managing choice quantity. Use when designing navigation, menus, feature sets, onboarding flows, or any interface where users must choose between options.
- ▌ Hooked Model 2 · flpbaladaDesign habit-forming products using the Hook cycle. Use when building engagement loops, improving retention, designing notifications, or creating products users return to without external prompting.
- ▌ Curiosity Gap 2 · flpbaladaCreate engagement through strategic information gaps that drive user action. Use when designing notifications, writing headlines, planning onboarding flows, or creating content that needs to capture and hold attention.
- ▌ Cognitive Load 2 · flpbaladaDesign experiences that optimize mental resources using Cognitive Load Theory. Use when designing interfaces, creating onboarding flows, planning information architecture, or improving task completion rates.
- ▌ Graph Thinking 2 · flpbaladaApply graph-based thinking to visualize complex relationships and solve problems non-linearly. Use when mapping dependencies, analyzing systems, exploring interconnected concepts, or designing architectures.
- ▌ Hypothesis Tree 2 · flpbaladaStructure complex questions into testable hypotheses. Use when validating product ideas, debugging problems, planning experiments, or breaking down ambiguous challenges into actionable research.
- ▌ Jobs To Be Done 2 · flpbaladaUnderstand customer motivations through job theory. Use when defining product strategy, conducting user research, identifying competitors, writing user stories, or reframing features around customer progress.
- ▌ Status Quo Bias 2 · flpbaladaUnderstand and design for users' preference for current state over change. Use when planning migrations, introducing new features, designing defaults, or overcoming resistance to product adoption.
- ▌ Cognitive Biases 2 · flpbaladaApply cognitive bias knowledge to product design and decision-making. Use when designing user experiences, analyzing user behavior, improving conversions, or ensuring ethical design practices.
- ▌ Theme Epic Story 2 · flpbaladaStructure product work hierarchically using themes, epics, and stories. Use when organizing backlogs, planning releases, communicating with stakeholders, or breaking down large initiatives into manageable work.
- ▌ Trust Psychology 2 · flpbaladaBuild trust signals that reduce perceived risk and enable user action. Use when designing landing pages, checkout flows, onboarding experiences, or any conversion point where user hesitation is a barrier.
- ▌ Fogg Behavior Model 2 · flpbaladaDesign behavior change using the B=MAP framework. Use when designing onboarding flows, improving conversion, building habits, increasing feature adoption, or understanding why users don't take desired actions.
- ▌ Business Model Canvas 2 · flpbaladaDesign and analyze business models using the Business Model Canvas framework. Use when evaluating startups, planning new products, pivoting existing businesses, or understanding how companies create and capture value.
- ▌ Halo Effect Psychology 2 · flpbaladaApply the halo effect in product design and UX. Use when designing first impressions, brand perception, feature presentation, or understanding how one positive attribute influences perception of others.
- ▌ Progressive Disclosure 2 · flpbaladaReduce complexity by revealing information progressively. Use when designing onboarding, complex forms, feature-rich interfaces, or any experience where showing everything at once would overwhelm users.
- ▌ Game Theory Tit For Tat 2 · flpbaladaApply Tit for Tat strategy for negotiations, relationships, and repeated interactions. Use when navigating workplace dynamics, building partnerships, handling conflicts, or designing systems with reciprocal interactions.
- ▌ Self Initiated Triggers 2 · flpbaladaDesign internal triggers for sustained user engagement. Use when building habit-forming features, improving retention without notifications, or transitioning users from external prompts to self-motivated engagement.
- ▌ Social Proof Psychology 2 · flpbaladaLeverage social proof principles to build trust and influence user behavior. Use when designing landing pages, adding testimonials, displaying user stats, or optimizing conversion elements with social validation.
- ▌ User Story Fundamentals 2 · flpbaladaCapture requirements from user perspective with structured user stories. Use when writing backlog items, defining acceptance criteria, prioritizing features, or communicating requirements between product and development.
- ▌ Loss Aversion Psychology 2 · flpbaladaLeverage loss aversion in product design and messaging. Use when designing retention features, pricing strategies, onboarding flows, or any experience where framing around potential loss can drive behavior.
- ▌ Skill Creator · flpbaladaCreate Claude Code custom skills with proper structure and metadata. Use when building new skills, setting up skill directories, or packaging skills for distribution.
- ▌ Learn · flpbaladaExtract one reusable skill pattern from current session, such as a recurring error fix, debugging tactic, tool combo, project convention, or workflow worth saving. Use when user asks to learn, remember, capture, or turn session knowledge into a skill. Ask before writing new skill files; skip one-off fixes.
- ▌ Kaizen · flpbaladaImprove processes through small continuous changes, waste reduction, and PDCA cycles. Use when optimizing workflows, retrospectives, team operations, quality problems, or incremental product-delivery improvements; avoid for visualizing flow only, root-cause analysis only, or large strategic redesign.
- ▌ Kanban · flpbaladaVisualize and improve delivery flow with Kanban. Use when managing work-in-progress, bottlenecks, queues, service classes, cycle time, or team workflow policies; avoid for broader continuous-improvement culture, root-cause analysis, or product hierarchy planning.
- ▌ Dogfood · flpbalada bundleDogfood a web app or local URL with exploratory QA, bug hunt, UX review, console checks, screenshots, videos, repro steps, and severity report. Use when user asks to test, QA, find issues, review quality, or explore site/app behavior. Do not inspect source code during testing.
- ▌ Routing · flpbaladaClassify inputs into specialized prompts, tools, models, agents, or workflows using route labels, confidence, fallback, and misroute review. Use when clear request categories need different handling for cost, latency, safety, quality, or domain. Do not use for sequential steps; use prompt-chaining. Do not use for dynamic decomposition; use orchestrator-workers.
- ▌ Electron · flpbaladaAutomate or test Electron desktop apps through agent-browser and Chrome DevTools Protocol, including Slack, VS Code, Discord, Figma, Notion, Spotify, and similar apps. Use when user asks to control, connect to, inspect, click, fill, screenshot, or interact with a native Electron app UI. Do not use for normal web URLs.
- ▌ Decompose · flpbaladaSplit an oversized component into focused helpers, hooks, and sub-components. Use when React/UI code mixes rendering, state, effects, handlers, data shaping, and repeated sections, or when a file is hard to scan. Preserve behavior and avoid generic abstractions. For general code restructuring use refactoring; for abstraction decisions beyond one component use code-architecture-wrong-abstraction.
- ▌ Five Whys · flpbaladaTrace a specific problem to systemic root causes with Five Whys. Use when investigating incidents, recurring bugs, churn, process failures, delays, or unexplained outcomes; require evidence at each step and avoid broad strategy analysis or blame-focused retrospectives.
- ▌ Hicks Law · flpbaladaReduce decision time by managing choice count and choice structure with Hick's Law. Use when designing menus, navigation, plans, filters, onboarding paths, settings, or feature sets with too many options; avoid for complex-task load, staged disclosure, or CTA visibility issues.
- ▌ Kano Model · flpbalada bundlePrioritize product features with the Kano model of customer satisfaction. Use when sorting feature ideas, roadmap items, requirements, or service attributes into must-haves, performance drivers, delighters, low-value work, and reverse effects; use to decide what to protect, improve, add, defer, remove, or validate.
- ▌ Para Method · flpbalada bundleOrganize information into Projects, Areas, Resources, and Archives. Use when setting up notes, files, knowledge bases, personal systems, or migrations from messy folders; avoid for product backlog hierarchy, workflow Kanban, or strategic portfolio planning.
- ▌ Refactoring · flpbaladaPlan and apply behavior-preserving code refactors. Use when restructuring target files, reducing complexity, improving maintainability, applying framework or language best practices, improving type models, or reorganizing code while preserving public behavior and contracts. For quick cleanup of recent edits use code-simplifier; for review-only architecture candidates use architecture-review.
- ▌ Deep Thinker · flpbaladaAnalyze ambiguous problems, hard decisions, root causes, product strategy, or tradeoffs with useful frameworks, assumptions, validation, and next actions. Use when user needs structured thinking before choosing a path.
- ▌ Explain Diff · flpbalada bundleExplain code diffs in Markdown, one changed file at a time. Use when user asks to explain unstaged changes, staged changes, a commit, commit range, branch diff, PR diff, or pasted diff. Ask for diff source when missing.
- ▌ Follow Goals · flpbalada bundleShape long-running autonomous work into one durable goal with stop condition, validation loop, checkpoints, progress format, and pause rules. Use for scoped, verifiable progress across migrations, refactors, prototypes, evals, retry loops, or prompt optimization; avoid loose backlog lists, one-shot answers, hidden preferences or unavailable context, and autonomous work that risks production without human approval.
- ▌ Hooked Model · flpbaladaDesign habit-forming product loops with trigger, action, variable reward, and investment. Use when improving retention, engagement loops, repeat use, notifications, or products meant to become routines; avoid for single-action conversion diagnosis better handled by Fogg B=MAP.
- ▌ Prd Delivery · flpbaladaDeliver a defined goal through orchestrated implementation and independent QA. Use when work should be delegated, tested against Given/When/Then requirements, and repaired until it passes.
- ▌ Code Reviewer · flpbaladaReview code for concrete defects and ranked risk. Use when asked to review diffs, pull requests, changed files, snippets, or implementation plans for bugs, security, performance, UX, API contracts, tests, concurrency, error handling, state/data hazards, accessibility, dependencies, or observability. Produces findings first with file:line evidence. For factual diff explanation use explain-diff; for architecture-only review use architecture-review.
- ▌ Curiosity Gap · flpbaladaCreate ethical information gaps that earn attention and resolve with real payoff. Use when writing headlines, notifications, teasers, onboarding reveals, or feature-discovery prompts; avoid fake urgency, vague clickbait, or habit-loop work better handled by Hooked or self-initiated triggers.
- ▌ Pest Analysis · flpbaladaAnalyze macro-environment forces with PEST political, economic, social, and technological factors. Use when assessing markets, expansion, regulation, industry change, strategic risks, or external business context; avoid for internal business-model design or user motivation research.
- ▌ To Milestones · flpbalada bundleBreak a PRD into linear, verifiable implementation milestones grounded in the codebase. Use when planning implementation checkpoints from product requirements.
- ▌ Cognitive Load · flpbaladaReduce unnecessary mental effort with Cognitive Load Theory. Use when complex workflows, onboarding, forms, information architecture, or feature-rich interfaces overwhelm users; separate intrinsic task difficulty from extraneous UI friction and avoid using this only for copy clarity or choice-count problems.
- ▌ Graph Thinking · flpbaladaModel complex systems as nodes, edges, flows, and dependencies. Use when mapping stakeholder networks, causal loops, product ecosystems, architecture dependencies, knowledge graphs, or non-linear strategy problems; avoid when a simple hierarchy, roadmap, or checklist is enough.
- ▌ Prd To Tickets · flpbalada bundleBreak a user-provided PRD into ordered, independently verifiable implementation tickets returned directly in the response.
- ▌ React Key Prop · flpbaladaChoose correct React key props for lists and remounts. Use when mapping arrays, rendering dynamic lists, sorting/filtering/reordering items, debugging list state bugs, avoiding index keys, or intentionally resetting component state with a key. For general local state updates use react-use-state; for effect-based resets use react-useeffect-avoid.
- ▌ Code Simplifier · flpbaladaSimplify recently changed code without changing behavior. Use after implementation when working code has excess nesting, repetition, indirection, unclear names, redundant branches, or needless abstraction. Scope stays near touched code and favors guard clauses and readability. For larger planned restructuring use refactoring; for extracting component pieces use decompose.
- ▌ Hypothesis Tree · flpbaladaBreak ambiguous questions into mutually useful hypotheses and tests. Use when validating product ideas, debugging uncertain causes, planning research, prioritizing experiments, or turning strategy questions into evidence plans; avoid for root-cause chains needing Five Whys.
- ▌ Jobs To Be Done · flpbaladaReframe product strategy around customer progress with Jobs to Be Done. Use when researching motivations, switching behavior, competitive alternatives, unmet needs, feature framing, or value propositions; avoid for backlog story syntax, delivery hierarchy, or business-model economics.
- ▌ Parallelization · flpbaladaSplit independent LLM work into concurrent branches, then merge, vote, rank, or compare outputs with a simple schema. Use when subtasks are isolated by item, source, section, test, or judge and latency or judgment quality matters. Do not use when one branch depends on another; use prompt-chaining.
- ▌ Prompt Chaining · flpbaladaBreak known LLM work into fixed sequential steps with handoff schemas, validation checks, retries, and final formatting. Use when later steps depend on earlier outputs or staged review reduces errors. Do not use for independent branches; use parallelization. Do not use when tasks must be discovered at runtime; use orchestrator-workers.
- ▌ React Hook Form · flpbalada bundleBuild or refactor React forms with React Hook Form. Use when working with useForm, register, handleSubmit, formState errors, defaultValues, validation rules, Controller, useController, FormProvider, useFieldArray, Zod or other resolvers, server submissions, and TypeScript form values. For simple local input state without React Hook Form use react-use-state.
- ▌ React Use State · flpbaladaUse React useState for simple local component state. Use when adding UI state, inputs, counters, selected IDs, active tabs, local arrays or objects, updater functions, initializer functions, or debugging stale reads and mutation bugs. Prefer derived values, useRef, useReducer, context, or server-state libraries when state should not live in useState.
- ▌ Status Quo Bias · flpbaladaDesign for user resistance to change and preference for the current state. Use when planning migrations, defaults, switching paths, feature adoption, workflow replacement, or rollout risk; distinguish from loss aversion by focusing on change friction, reversibility, and transition design.
- ▌ Cognitive Biases · flpbalada bundleIdentify cognitive biases shaping product decisions and user behavior. Use when auditing decision points, conversion flows, pricing, framing, defaults, or research interpretation; avoid when a narrower bias skill such as loss aversion, status quo bias, halo effect, social proof, or Hick's Law directly fits.
- ▌ Effort Estimator · flpbaladaEstimate engineering effort from scope, risk, unknowns, and verification cost. Use when sizing features, splitting work, planning sprints, comparing implementation options, or deciding whether a task is XS through XL, provided enough task detail exists for a rough estimate; avoid for product value, requirements quality, or business-case analysis.
- ▌ Summarize Branch · flpbaladaWrite a concise PR description from branch commit messages, using `fixes` for fix commits and `implements` otherwise. Use when user needs pull request text, branch summary, or review-ready description from git history. Do not draft commit messages; use conventional-commit.
- ▌ Theme Epic Story · flpbaladaStructure product work from strategic themes to epics, stories, and tasks. Use when organizing backlogs, roadmaps, releases, stakeholder communication, or large initiatives into outcome-linked delivery units; avoid for writing one story only, requirements analysis, or effort estimates.
- ▌ Trust Psychology · flpbaladaAdd trust signals that reduce perceived risk before important user actions. Use for signup, checkout, onboarding, landing pages, pricing, guarantees, security, support, and cancellation reassurance; distinguish from social proof, halo effect, and cognitive fluency by focusing on risk.
- ▌ Naming Cheatsheet · flpbaladaName code identifiers clearly and consistently. Use when naming or reviewing variables, functions, booleans, classes, files, modules, React hooks, event handlers, props callbacks, error values, and domain concepts; reducing ambiguity, duplicated context, contractions, or misleading singular/plural names. For larger code-quality review use code-reviewer.
- ▌ Prd Goal Delivery · flpbaladaDrive PRD implementation through a durable /goal, scoped parallel implementation agents, independent QA ownership, acceptance evidence, and persona-based test instructions. Use when a PRD must be delivered end-to-end and every acceptance criterion must be verified before marking the goal complete.
- ▌ Prd Loc Estimator · flpbalada bundleEstimate line additions and deletions from a PRD or spec by reading the requirements and inspecting the target repo. Use when the user asks for changed LOC, additions, deletions, diff size, PR size, or implementation size before building.
- ▌ Project Structure · flpbaladaOrganize React, Next.js, or TypeScript projects with feature-based architecture. Use when starting or reorganizing an app, deciding where files belong, separating app/features/shared layers, preventing cross-feature imports, designing module boundaries, or applying Bulletproof React-style structure. For high-level architecture tradeoffs use architecture-review; for single-component splitting use decompose.
- ▌ Prompt Simplifier · flpbaladaSimplify prompts, system instructions, workflows, rules, and agent playbooks while preserving behavior. Use when logic has too many branches, nested conditions, contradictions, repeated rules, vague failure paths, or inconsistent outputs. Do not rewrite product requirements; use to-prd for PRD conversion.
- ▌ Value Realization · flpbalada bundleCheck whether users can discover, understand, believe, and experience product value. Use when evaluating concepts, activation, onboarding, adoption, messaging, time-to-value, or unclear product direction; avoid for business-model economics, JTBD motivation research, or CTA-level optimization.
- ▌ Letter From Future · flpbalada bundleCreate a letter-from-future planning artifact for startup, product, roadmap, pivot, project kickoff, quarterly planning, or stakeholder alignment. Use when user needs to describe a desired future, backcast milestones, connect vision to customer value, and surface risks, metrics, and next actions. Do not use for formal PRDs; use to-prd.
- ▌ React Use Callback · flpbaladaDecide when to use React useCallback. Use when callback identity affects memoized children, dependency arrays, custom hooks, event handlers passed through props, or unnecessary re-renders. Avoid defaulting to useCallback for every function. For state update correctness use react-use-state; for effect dependency alternatives use react-useeffect-avoid.
- ▌ Architecture Review · flpbaladaReview software architecture before editing. Use when asked to assess module boundaries, interfaces, layering, ownership, seams, adapters, locality, coupling, shallow modules, or refactor candidates. Produces ranked architecture candidates and waits for explicit approval before changing code. For normal code review use code-reviewer; for approved behavior-preserving edits use refactoring.
- ▌ Codebase Slop Audit · flpbalada bundleDetect sloppy-code signals with repo-wide search metrics and sampled evidence. Use when asked to audit codebase quality, "vibe coding", `isRecord`, broad `Record<string, unknown>` guards, fallback usage, excessive null guards, non-null assertions, unsafe type assertions, `node:*` imports in browser/shared code, swallowed errors, TODO debt, or code smell hotspots before refactoring.
- ▌ Conventional Commit · flpbaladaDraft or review Conventional Commits messages with type, optional scope, imperative summary, body, footer, and breaking-change notes. Use when user asks for a commit message, commit title and body, changelog-safe wording, or commit-format review. Do not use for PR descriptions; use summarize-branch.
- ▌ Deliberate Practice · flpbaladaDesign focused practice loops for skill improvement. Use when learning a skill, breaking a plateau, creating training routines, onboarding practitioners, or choosing feedback and challenge levels; avoid for generic productivity, knowledge organization, or project delivery planning.
- ▌ Evaluator Optimizer · flpbaladaRun an evaluator-optimizer loop by generating candidate outputs, scoring against a rubric or tests, revising, and stopping on pass, budget, or plateau. Use when quality criteria are explicit and iterative refinement is cheaper than failure; avoid when no reliable evaluation signal exists, speed matters more than polish, outputs are high-risk and require human review, or revision may drift from user intent.
- ▌ Fogg Behavior Model · flpbaladaDiagnose behavior change with B=MAP motivation, ability, and prompt. Use when users do not take a target action, onboarding stalls, conversion drops, feature adoption lags, or prompts fire at the wrong moment; avoid for full habit-loop design better handled by Hooked.
- ▌ Gpt5 5 Prompt Grill · flpbalada bundlePressure-test, reduce, and rewrite prompts for GPT-5.5. Use when the user asks to grill, audit, critique, harden, improve, optimize, simplify, de-noise, or rewrite a prompt, system prompt, developer instruction, agent playbook, or tool-use workflow specifically for GPT-5.5; especially when it may contain no-op instructions, contradictions, vague rules, missing success criteria, missing output rules, missing validation, unsupported claims, or unclear stop rules.
- ▌ Render Reading Diff · flpbalada bundleFind and abridge important or meaningful diff changes into an HTML reading review. Use for latest commit, staged or working-tree changes, a revision, range, branch diff, or supplied unified diff.
- ▌ Opencode Skill Usage · flpbalada bundleList completed OpenCode skill calls ranked by usage count. Use when users ask for most-used skills, skill usage counts, skill statistics, or a ranked skill usage table.
- ▌ Orchestrator Workers · flpbaladaPlan and run dynamic worker decomposition with a central orchestrator, narrow worker jobs, output schemas, replanning rounds, and synthesized results. Use when task shape is unknown upfront and subtasks must be assigned at runtime. Do not use for fixed sequences; use prompt-chaining. Do not use for independent known branches; use parallelization.
- ▌ Discuss Code · flpbalada bundleDiscuss code critically before or instead of editing. Use when user asks for a compact opinion on code, a diff, snippet, design, naming, logic, simplicity, structure, or maintainability, and wants findings plus smallest useful fixes. For formal risk-ranked pull request review use code-reviewer; for architecture candidates use architecture-review; for actual cleanup edits use code-simplifier or refactoring.
- ▌ Answer Open Questions · flpbaladaAnalyze a list of open questions and suggest up to three answers for each. Use when the user wants options, recommendations, or help resolving multiple unanswered questions.
- ▌ Business Model Canvas · flpbaladaMap value creation, delivery, and capture with the Business Model Canvas. Use when evaluating startups, pivots, product strategy, revenue streams, cost structure, partners, channels, or business-model coherence; avoid for deep customer-job research, roadmap breakdowns, or macro-environment scans.
- ▌ CSS Container Queries · flpbaladaApply CSS container queries for parent-size responsive components. Use when cards, widgets, panels, sidebars, forms, or component-library elements must adapt to their container width with @container, container-type, container-name, or Tailwind @container variants. Use media queries instead for page-level viewport layout, global breakpoints, or full-page composition.
- ▌ React Useeffect Avoid · flpbalada bundleAvoid unnecessary React useEffect and choose better alternatives. Use when reviewing effects, derived state, prop-to-state copies, event handling, form resets, extra renders, stale synchronization, or async/server data patterns. Keep useEffect for external systems like subscriptions, timers, browser APIs, third-party widgets, analytics, or document title. For callback identity use react-use-callback.
- ▌ Requirements Analyzer · flpbaladaAnalyze feature requirements for clarity, scope, risk, assumptions, and testability before implementation. Use when specs are vague, acceptance criteria are missing, edge cases are unclear, or work needs splitting; avoid for writing full user stories or estimating effort only.
- ▌ Requirements Delivery · flpbaladaDeliver a defined goal and its requirements through orchestrated task decomposition, implementation agents, and independent QA. Use when scope may come from a prompt, specification, issue, referenced documents, or mixed sources and every blocking requirement must be verified before completion.
- ▌ Halo Effect Psychology · flpbaladaUse halo-effect analysis for first impressions and perception spillover. Use when brand polish, visual quality, flagship features, reviews, or spokesperson credibility may shape trust in unrelated product areas; avoid for general trust, social proof, or readability problems.
- ▌ Progressive Disclosure · flpbaladaReveal complexity in stages so users see what they need when they need it. Use for onboarding, forms, settings, advanced options, dashboards, or dense interfaces; avoid when problem is simply too many choices, weak copy clarity, or overall task complexity.
- ▌ Game Theory Tit For Tat · flpbaladaUse Tit for Tat to manage repeated interactions with reciprocity, cooperation, and boundaries. Use for workplace dynamics, partnerships, negotiations, conflicts, vendor relationships, or product systems with observable reciprocal behavior; avoid one-shot or zero-sum situations, severe abuse or safety issues, hidden actions where reciprocity cannot be observed, and unethical or illegal retaliation.
- ▌ Self Initiated Triggers · flpbaladaBuild internal triggers that make users return from their own needs, emotions, or routines. Use when reducing notification dependence, strengthening retention, mapping return moments, or moving from external prompts to self-initiated use; avoid for full habit-loop design or one-time CTA conversion.
- ▌ Social Proof Psychology · flpbaladaUse credible evidence from relevant others to reduce uncertainty. Use when selecting testimonials, reviews, customer logos, usage stats, expert endorsements, or peer proof near decisions; avoid generic trust work, fake popularity, or halo effects from brand polish alone.