Browse All Prompts

Measure and achieve product-market fit using multiple signals. PMF indicators: 1. Sean Ellis test: >40% of users would be 'very disappointed' if they couldn't use product anymore. 2. Retention curves: cohorts flatten to horizontal line (not declining). 3. Organic growth: word-of-mouth driving 30%+ of new signups. 4. Usage intensity: users engaging multiple times per week. 5. Net Promoter Score >50 and growing. Measurement cadence: survey users quarterly, analyze retention monthly, track referrals weekly. Early PMF signs: customers pulling product from you, usage growing organically, positive unit economics emerging. Pre-PMF: focus on retention over growth. Post-PMF: optimize growth engines. Tools: Amplitude for retention, Delighted for NPS, internal surveys for disappointment test. Document learnings about ICP (ideal customer profile) refinement.

Document APIs with OpenAPI/Swagger. Structure: 1. OpenAPI specification (YAML/JSON). 2. Paths for endpoints. 3. Request/response schemas. 4. Parameter descriptions. 5. Authentication schemes. 6. Example requests/responses. 7. Error codes documentation. 8. Interactive try-it-out. Use Swagger UI for visualization. Generate from code or design-first. Keep docs in sync with implementation.

Use restorative circles to address classroom conflicts instead of punitive measures. Scenario: Two students had a verbal argument. Process: 1. Preparation: Meet with each student individually to hear their perspective. 2. The Circle: Bring both students, a facilitator (teacher/counselor), and possibly a trusted peer for each. 3. Opening: Use a talking piece to ensure one person speaks at a time. 4. Questions: 'What happened?' 'What were you thinking at the time?' 'Who has been affected?' 'What do you need to make things right?' 5. Agreement: Students collaboratively decide on a plan to repair the harm (e.g., apology, replacing a damaged item, working together on a task). 6. Follow-up: Check in with students the next day. Goal: focus on repairing relationships and learning from mistakes.

Create a multi-page application with Parcel's zero-config approach. Setup: 1. Multiple HTML entry points. 2. Automatic code splitting per page. 3. Shared chunks for common dependencies. 4. Hot module replacement. 5. Image optimization and resizing. 6. PostCSS and Sass support out-of-box. 7. Environment variable injection. 8. Production builds with tree-shaking. No webpack config needed. Use @parcel/transformer-typescript and implement service worker for offline support.

Teach students to 'think about their thinking'. Strategies: 1. Pre-assessment: Before a unit, have students complete a 'What I Know, What I Want to Know' (KWL) chart. 2. The Muddiest Point: During a lesson, pause and ask students to write down the 'muddiest point'—what is least clear to them. 3. Exam Wrappers: After a test, have students analyze their performance. Ask: 'How did you study?' 'What types of questions did you miss?' 'What will you do differently next time?' 4. Reflective Journals: Prompt students to reflect on their learning process weekly. 'What strategy worked well for you this week?' 'Where did you get stuck?' Goal: move students from passive recipients to active managers of their own learning.

Leverage Valtio's proxy magic for state. Usage: 1. proxy() creates mutable state. 2. Direct property mutations. 3. snapshot() for immutable reads. 4. useSnapshot hook in React. 5. subscribe() for listeners. 6. Nested objects auto-tracked. 7. Derive computed values. 8. Works outside React. Simple mental model: mutate state directly, components auto-update. Use with class instances for OOP patterns.

Leverage AI to provide faster, more personalized feedback on student writing. Tools: Writable, Turnitin Feedback Studio, ChatGPT. Workflow: 1. Students submit essays to an AI-powered platform. 2. The AI provides instant feedback on grammar, spelling, sentence structure, and style. 3. The AI can also check for plagiarism and assess against a rubric. 4. Teacher reviews the AI's comments, adds higher-level feedback on argumentation and critical thinking, and adjusts the AI-generated score. 5. Students use the combined feedback to revise their work. Benefits: saves teacher time on low-level corrections, provides immediate feedback to students, allows teachers to focus on more substantive comments. Ethical consideration: teach students how to use AI as a tool, not a crutch.

Document components effectively with Storybook 7. Setup: 1. CSF3 format for stories. 2. Autodocs for prop table generation. 3. Controls addon for prop manipulation. 4. Actions addon for event logging. 5. Interactions testing with @storybook/test. 6. Accessibility checks with a11y addon. 7. Design tokens documentation. 8. MDX for custom documentation pages. Use composition for multiple projects and implement visual testing with Chromatic.

Replace a traditional research paper with a podcast project. Subject: US History. Task: Students work in groups of 3-4 to create a 15-minute podcast episode on a historical event. Process: 1. Research Phase: Students gather information from primary and secondary sources. 2. Scripting Phase: Students write a collaborative script, including narration, sound effects, and potential interview segments. 3. Recording & Editing Phase: Students use tools like Audacity or Soundtrap to record and edit their podcast. 4. Publishing: Episodes are uploaded to a class website or platform like SoundCloud. Assessment Rubric: historical accuracy, narrative structure, audio quality, collaboration, and source citation. Allows for creativity and develops 21st-century communication skills.

Manage innovation pipeline from idea generation to product launch. Innovation stages: 1. Idea generation: customer feedback, competitor analysis, technology trends. 2. Concept validation: user interviews, prototype testing, market research. 3. Business case development: market size, revenue model, ROI analysis. 4. MVP development: minimum viable product with core features. 5. Market testing: limited release, feedback collection, iteration. 6. Scale-up: full product launch and growth optimization. Stage gates: defined criteria for advancing ideas between stages. Example criteria: Problem validation (100+ customer interviews), Market size ($100M+ TAM), Technical feasibility (prototype built). Resource allocation: 70% sustaining innovation (core product), 20% adjacent opportunities, 10% disruptive bets. Metrics: ideas in pipeline, conversion rates between stages, time-to-market. Portfolio management: balance short-term revenue with long-term growth bets. Innovation culture: hackathons, innovation time, fail-fast mentality.

Implement a 15-minute daily morning meeting in an elementary classroom. Structure (based on Responsive Classroom): 1. Greeting (3 mins): Students greet each other by name (e.g., handshake, wave, fun greeting). Builds community. 2. Sharing (4 mins): 2-3 students share something about their life. Others practice active listening and asking thoughtful questions. 3. Group Activity (5 mins): A quick, fun activity to build teamwork and communication (e.g., 'Count to 20 as a class', a short song). 4. Morning Message (3 mins): Teacher reads a daily message that sets a positive tone and outlines the day's learning. Establishes a safe, predictable start to the day and builds social skills.

Implement component testing with Cypress. Workflow: 1. Mount React/Vue components in isolation. 2. cy.get() for element selection. 3. Intercept API calls with cy.intercept(). 4. Test user interactions (click, type, drag). 5. Visual viewport testing. 6. Custom commands for reusability. 7. Fixtures for test data. 8. Time travel debugging. Use with TypeScript and implement accessibility testing with cypress-axe plugin.

Shift from traditional to student-led conferences. Preparation: 1. Students compile a portfolio of their work (successes and challenges). 2. Students complete a self-reflection sheet on their progress, goals, and areas for improvement. 3. Students practice presenting their portfolio to peers. The Conference (20 mins): 1. Student welcomes parents and teacher. 2. Student presents their portfolio, explaining their work and learning process. 3. Student discusses their self-reflection and goals for the next quarter. 4. Parents and teacher ask questions and provide feedback. 5. All parties co-sign the goal-setting sheet. Benefits: increases student ownership and accountability, develops communication skills, provides parents with a more authentic view of their child's learning.

Write compelling grant proposals with high funding success rates. Proposal structure: 1. Specific Aims (1 page): state problem clearly, propose solution, highlight innovation and significance. 2. Research Strategy: Significance (why important), Innovation (what's new), Approach (how to do it). 3. Budget justification: personnel (effort percentages), equipment, supplies, indirect costs. Pre-writing: 1. Read funding agency priorities and review criteria. 2. Study successful proposals in your field. 3. Contact program officer for informal feedback on concept. Writing strategy: 1. Lead with impact: what difference will this make? 2. Use visual elements: figures, flowcharts, timelines. 3. Address reviewer concerns preemptively. 4. Get external reviews before submission. Common mistakes: aims too ambitious, insufficient preliminary data, weak methodology, unclear significance. Timeline: start 3-6 months before deadline, allow time for institutional review.

Organize a formal debate on the topic: 'Should the Electoral College be abolished?' Structure: Lincoln-Douglas or team-based format. Teams: Affirmative (pro-abolition) and Negative (con-abolition). Roles: speakers, researchers, rebuttal planners. Timeline: 1. Research (1 week): Teams gather evidence and prepare arguments. 2. Constructive Speeches (8 mins each team): Present initial arguments. 3. Cross-Examination (3 mins after each speech): Opposing team asks clarifying questions. 4. Rebuttal Speeches (5 mins each team): Address and refute opponents' arguments. 5. Closing Statements (3 mins each team): Summarize key points. Assessment: rubric based on strength of argument, use of evidence, rebuttal effectiveness, and public speaking skills. Teacher acts as moderator.

Create a lightweight desktop app with Tauri. Benefits: 1. Rust backend for performance and security. 2. Native webview (no bundled Chromium). 3. React/Vue/Svelte frontend. 4. Commands for Rust-to-JS communication. 5. File system API with permissions. 6. System tray and notifications. 7. Smaller bundle size vs Electron. 8. Window customization and multi-window support. Use @tauri-apps/api and implement plugin system for extensibility.

Create a role-playing simulation of the Cuban Missile Crisis. Roles: President Kennedy, Robert Kennedy, military advisors (Joint Chiefs), Soviet Ambassador, etc. Scenario: Students receive role-specific briefing documents with classified information and objectives. Process: 1. Students meet in their advisory groups to discuss options. 2. The 'President' facilitates a series of meetings where advisors present their cases (e.g., blockade vs. air strike). 3. The 'President' makes a decision. 4. Teacher reveals the historical outcome. Debrief: Students reflect on the pressures of decision-making, the role of information, and the consequences of different choices. Compare their simulation outcome to the actual historical events.

Create engaging motion graphics using 12 principles of animation and timing theory. Core animation principles: 1. Squash and stretch: volume preservation during movement for natural feel. 2. Anticipation: prepare audience for main action (wind-up before throw). 3. Ease in/out: gradual acceleration/deceleration mimics natural movement. 4. Follow through: secondary elements continue moving after primary action stops. Timing fundamentals: 1. 24 fps standard for cinematic feel, 30 fps for broadcast, 60 fps for smooth UI. 2. Rule of thirds for duration: setup (1/3), action (1/3), resolution (1/3). 3. Attention span: key message delivery within first 3 seconds. Typography animation: 1. Staggered reveals: 0.1-0.2 second delays between elements. 2. Kinetic typography: text movement supports meaning and emotion. 3. Reading time: allow 250 words per minute reading speed. Software techniques: After Effects keyframe interpolation, easing curves for natural motion, pre-composition for complex animations. Export optimization: H.264 for video, GIF for web loops under 3MB, Lottie for interactive web animations. Testing: preview on target devices, gather feedback on pacing and clarity.

Develop a school improvement plan based on data analysis. Data Sources: 1. Academic: standardized test scores, graduation rates, course failure rates. 2. Culture/Climate: student and staff survey results (e.g., Panorama), attendance data, discipline referrals. Process: 1. Data Dig: Leadership team analyzes data to identify 2-3 priority areas (e.g., '9th-grade math proficiency is low', 'student sense of belonging is declining'). 2. Root Cause Analysis: Use a 'Fishbone Diagram' to brainstorm potential causes for each problem. 3. Goal Setting: Create SMART goals for each priority area (e.g., 'Increase 9th-grade math proficiency by 10% by May'). 4. Action Plan: Define specific strategies, person responsible, timeline, and required resources. 5. Monitor Progress: Review progress toward goals at monthly leadership meetings.

Implement navigation in React Native apps. Patterns: 1. Stack navigator for hierarchical screens. 2. Tab navigator for main sections. 3. Drawer navigator for side menu. 4. Deep linking and universal links. 5. Screen transitions and gestures. 6. Nested navigators composition. 7. Authentication flow routing. 8. Persistent navigation state. Use React Navigation v6 with TypeScript for type-safe routes and implement header customization.

Teach solving algebraic equations using manipulatives. Concept: Solving '2x + 3 = 11'. Manipulatives: Use cups to represent the variable 'x' and two-color counters for integers. Process (Concrete-Representational-Abstract): 1. Concrete: Students model the equation on a mat. They place 2 cups and 3 positive counters on one side, and 11 positive counters on the other. To solve, they remove 3 counters from each side, then divide the remaining 8 counters equally between the 2 cups. They find each cup (x) equals 4. 2. Representational: Students draw pictures of the cups and counters to solve similar problems. 3. Abstract: Students transition to solving the equation using only symbols and numbers. This progression builds conceptual understanding before procedural fluency.

Analyze change over time using growth curve models. Data structure: repeated measures nested within individuals (Level 1: time, Level 2: person). Models in R lme4 or HLM software: 1. Unconditional growth model: test for linear change over time. 2. Conditional growth models: add predictors of intercept and slope. 3. Piecewise growth: different slopes for different time periods. 4. Nonlinear growth: quadratic, exponential, or logistic growth patterns. Model building: 1. Plot individual trajectories to visualize patterns. 2. Test unconditional means model for ICC. 3. Add time variable, test linear growth. 4. Add predictors systematically. 5. Test model assumptions (linearity, normality, homoscedasticity). Missing data: use maximum likelihood estimation (handles MAR data). Report: fixed effects (average growth), random effects (individual variation), model fit indices (AIC, BIC).

Conduct an outdoor lesson in a schoolyard or local park. Topic: Ecosystems. Activity: 'Bio-Blitz'. 1. Preparation: Define a 10x10 meter area. Provide students with field guides, magnifying glasses, and data collection sheets. 2. The Blitz (30 mins): In small groups, students identify and count as many different species of plants and animals as they can find in their designated area. They can use apps like iNaturalist for identification. 3. Data Analysis (15 mins): Back in the classroom, groups pool their data to calculate the biodiversity of the area. Create a food web diagram based on the organisms they found. 4. Reflection (10 mins): Discuss human impact on the local ecosystem. Fosters observation skills, appreciation for nature, and understanding of ecological concepts.

Design Flutter apps with platform-adaptive UI. Architecture: 1. StatelessWidget and StatefulWidget patterns. 2. Provider or Riverpod for state management. 3. Platform checks for iOS/Android differences. 4. Cupertino widgets for iOS feel. 5. Material Design 3 for Android. 6. Responsive layouts with LayoutBuilder. 7. Custom theming with ThemeData. 8. Navigation with GoRouter. Use const constructors for performance and implement accessibility with Semantics.

Set up a classroom economy to teach financial concepts. System: 1. Jobs: Students apply for and hold classroom jobs (e.g., line leader, tech support, librarian), earning a weekly 'salary' in classroom currency. 2. Income: Students earn money for their job and bonuses for positive behavior. 3. Expenses: Students pay 'rent' for their desk and 'fines' for breaking class rules. 4. Banking: Students use a ledger to track their deposits and withdrawals. 5. Market: Hold a monthly 'store' where students can spend their earnings on small prizes or privileges. Advanced concepts: introduce 'interest' for savings, 'loans' for large purchases, and 'taxes' to fund class projects. Teaches responsibility, basic economics, and money management skills.

Master ghostwriting by capturing authentic client voice while maintaining professional standards. Voice analysis process: 1. Sample collection: existing writing, speeches, interviews, social media posts. 2. Pattern identification: sentence structure, vocabulary preferences, humor style. 3. Interview sessions: ask about influences, communication style, key messages. 4. Voice profile creation: tone characteristics, topics of expertise, personal anecdotes. Voice matching techniques: 1. Syntax mimicry: sentence length patterns, complexity levels. 2. Vocabulary alignment: technical vs. casual language, industry jargon. 3. Perspective consistency: optimistic vs. cautious outlook, formal vs. conversational. 4. Signature phrases: recurring expressions, unique metaphors. Content development: 1. Outline approval: structure and key points before writing. 2. Draft iterations: initial version, client feedback, refinements. 3. Fact verification: accuracy of claims, proper attribution. 4. Final review: client approval before publication. Professional boundaries: 1. Credit agreements: byline attribution, recognition terms. 2. Confidentiality: non-disclosure of proprietary information. 3. Intellectual property: ownership rights, future use permissions. Project types: books, articles, speeches, blog posts, social media content, thought leadership pieces.

Integrate short mindfulness activities to improve focus and reduce anxiety. Activities (1-3 minutes): 1. Mindful Breathing: 'Belly Buddies'. Younger students lie down with a small stuffed animal on their belly and watch it rise and fall as they breathe. Older students can do 'box breathing' (inhale for 4, hold for 4, exhale for 4, hold for 4). 2. Mindful Listening: Students close their eyes and listen for sounds near and far, identifying as many as they can. 3. Mindful Seeing: Students closely observe a small object (e.g., a raisin, a leaf) as if they've never seen it before. 4. Body Scan: Students bring awareness to each part of their body, from toes to head. Use these activities after recess, before a test, or during transitions.

Create Android UI with Jetpack Compose. Structure: 1. Composable functions for UI components. 2. remember and mutableStateOf for state. 3. LazyColumn for efficient lists. 4. Modifier chain for styling. 5. ViewModel integration. 6. Material 3 theming. 7. Side effects with LaunchedEffect. 8. Navigation component for screens. Use Accompanist for additional utilities and implement animations with animateContentSize.

Teach students to analyze primary sources like a historian. Framework: Sourcing, Contextualizing, Close Reading, Corroborating (Stanford History Education Group - SHEG). Activity: Give students two primary source documents about the Boston Massacre—one from a British officer, one from a colonial patriot. Analysis Steps: 1. Sourcing: Who wrote this? When? Why? Is it reliable? 2. Contextualizing: What was happening at the time that might influence this account? 3. Close Reading: What claims does the author make? What words do they use to persuade the reader? 4. Corroborating: How do the two accounts differ? Where do they agree? Which account is more believable and why? This moves students from memorizing facts to interpreting evidence.

Develop next generation of researchers through effective mentoring. Mentoring models: 1. Dyadic: traditional one-on-one mentor-mentee relationship. 2. Team mentoring: multiple mentors with different expertise areas. 3. Peer mentoring: lateral relationships between researchers at similar career stages. 4. Group mentoring: mentor works with cohort of mentees simultaneously. Mentoring competencies: 1. Research skills: methodology, analysis, writing, grant writing. 2. Professional development: networking, career planning, work-life balance. 3. Personal support: confidence building, resilience, identity development. Structure and process: 1. Goal setting: specific, measurable objectives for mentoring relationship. 2. Regular meetings: monthly face-to-face or virtual meetings with agenda. 3. Progress monitoring: quarterly reviews of goal achievement and relationship satisfaction. 4. Feedback: bidirectional feedback on mentoring effectiveness. Training programs: 1. Mentor training: active listening, giving feedback, cultural competence. 2. Mentee training: goal setting, communication, relationship management. Evaluation: surveys, focus groups, career outcome tracking for evidence-based improvement.

Design an engaging 90-minute PD session on a new instructional strategy. Agenda: 1. Why (10 mins): Start with research or data showing the need for the strategy. 2. What (20 mins): Clearly explain and model the strategy. Show a video of it in action. 3. How (30 mins): Active engagement. Have teachers try the strategy themselves (e.g., plan a short lesson segment using it). 4. What If (15 mins): Facilitate a discussion about potential challenges and solutions for implementation in their own classrooms. 5. Now What (15 mins): Teachers set a specific goal for how they will try the strategy in the next week. Provide a resource handout. Avoid 'sit and get'; prioritize active learning and collaboration.

Build type-safe APIs with tRPC. Architecture: 1. Define routers with input/output schemas. 2. Zod for runtime validation. 3. Automatic TypeScript inference. 4. React Query integration for client. 5. Middleware for auth and logging. 6. Context for user sessions. 7. Subscriptions with WebSockets. 8. Error handling with TRPCError. No code generation needed. Use with Next.js or standalone Express server.

Plan a Tier 2 reading intervention for a small group of 3rd graders. Target Skill: Reading fluency. Group Size: 4-5 students. Frequency: 3 times a week for 30 minutes. Structure: 1. Warm-up (5 mins): Practice sight words with flashcards. 2. Modeling (5 mins): Teacher models fluent reading of a short, instructional-level passage, emphasizing prosody and pacing. 3. Choral Reading (5 mins): Teacher and students read the passage aloud together. 4. Partner Reading (10 mins): Students take turns reading the passage to a partner. Teacher provides feedback. 5. Progress Monitoring (5 mins): Once a week, conduct a 1-minute timed reading of a new passage to track words correct per minute (WCPM). Graph progress to show growth. Intervention should be systematic and data-driven.

Master poetic techniques for powerful creative expression and emotional resonance. Poetic devices: 1. Metaphor: direct comparison without 'like' or 'as' (life is a journey). 2. Simile: comparison using 'like' or 'as' (brave as a lion). 3. Personification: human qualities to non-human objects. 4. Alliteration: repeated initial consonant sounds. 5. Assonance: repeated vowel sounds within lines. Form structures: 1. Free verse: no prescribed rhyme or meter, natural speech patterns. 2. Sonnet: 14 lines, specific rhyme schemes (Shakespearean, Petrarchan). 3. Haiku: 5-7-5 syllable structure, nature imagery, moment capture. 4. Villanelle: 19 lines, two refrains, specific rhyme pattern. Imagery techniques: 1. Sensory details: sight, sound, smell, taste, touch descriptions. 2. Concrete specifics: particular objects rather than abstractions. 3. Juxtaposition: contrasting images for emotional impact. Line and stanza craft: 1. Enjambment: lines flowing into next without grammatical pause. 2. Caesura: deliberate pause within line for emphasis. 3. White space: strategic use of silence, breath, reflection. Revision process: multiple drafts focusing on word choice, rhythm, emotional truth, unnecessary word elimination.

Create a digital escape room for a unit review using Google Forms. Theme: 'Escape the Mad Scientist's Lab' for a science unit. Structure: 1. Create a Google Form with multiple sections. 2. Set up 'response validation' for each question, so students can only proceed to the next section if they answer correctly. This acts as the 'lock'. 3. The questions are puzzles related to the unit content (e.g., a riddle about mitosis, a coded message with vocabulary words). 4. The final section reveals a 'You Escaped!' message. 5. Use a storyline to connect the puzzles. Share the form with students to complete in small groups. Promotes collaboration, problem-solving, and engagement.

Implement SWR for optimal data experience. Pattern: 1. useSWR hook with cache key. 2. Return stale data immediately. 3. Revalidate in background. 4. Dedupe simultaneous requests. 5. Focus revalidation. 6. Interval polling for real-time feel. 7. Error retry with exponential backoff. 8. Mutation with useSWRMutation. Use globally for all requests and implement dependent fetching for serial queries.

Set up and manage a class blog to provide an authentic audience for student writing. Platform: Edublogs, Kidblog, or a private Blogger site. Process: 1. Setup: Create the blog, establish categories (e.g., book reviews, science reports, creative writing), and teach students how to use the platform. 2. Digital Citizenship: Teach lessons on appropriate online commenting and respecting intellectual property. 3. Writing & Publishing: Students draft posts, receive peer and teacher feedback, revise, and then publish their work on the blog. 4. Audience: Share the blog link with parents and other classes. Encourage comments from readers. 5. Student Roles: Assign student editors, moderators, and social media managers (for a closed class account). Turns writing assignments into meaningful communication.

Control for confounding variables in observational studies. Design-based controls: 1. Randomization: Random assignment eliminates selection bias. 2. Restriction: limit study to homogeneous group (e.g., only males, specific age range). 3. Matching: match cases and controls on potential confounders (age, gender, education). Analysis-based controls: 1. Stratification: analyze results within strata of confounder levels. 2. Multiple regression: include confounders as covariates in regression model. 3. Propensity score matching: calculate probability of exposure, match on propensity scores. 4. Instrumental variables: use natural randomization when available. Assessment: Create directed acyclic graphs (DAGs) to identify confounders vs. mediators vs. colliders. Use causal inference framework to determine which variables to control. Report all controlled variables and rationale for inclusion.

Design a systematic literature review following PRISMA guidelines. Protocol steps: 1. Define research question using PICO framework (Population, Intervention, Comparison, Outcome). 2. Develop search strategy: identify 3-5 databases (PubMed, Scopus, Web of Science), create Boolean search terms, set inclusion/exclusion criteria. 3. Screen titles/abstracts independently by 2 reviewers, resolve conflicts with third reviewer. 4. Full-text review using predefined criteria. 5. Data extraction using standardized forms (study design, sample size, outcomes, bias assessment). 6. Quality assessment using appropriate tools (Cochrane Risk of Bias, Newcastle-Ottawa Scale). 7. Synthesize findings narratively or through meta-analysis if appropriate. Document decisions transparently. Register protocol in PROSPERO before starting.

Use Jotai's atomic approach to state. Concepts: 1. atom() for primitive state. 2. Derived atoms with get(). 3. Async atoms for data fetching. 4. atomFamily for dynamic atoms. 5. useAtom hook like useState. 6. Focus on specific atoms. 7. No string keys needed. 8. Works with Suspense. Minimal re-renders due to fine-grained subscriptions. Integrate with localStorage atoms for persistence.

Practice test-driven development. Workflow: 1. Write failing test first (Red). 2. Write minimal code to pass (Green). 3. Refactor while keeping tests green. 4. Repeat cycle. Benefits: Better design, confidence, documentation. Write tests for: edge cases, error handling, happy path. Use describe/it structure. Keep tests fast and isolated. Mock external dependencies.

Write clear user stories with testable acceptance criteria. Format: 'As a [persona], I want [functionality], so that [benefit].' Example: 'As a returning customer, I want to save my payment information, so that I can checkout faster on future purchases.' Acceptance criteria using Given-When-Then: Given I'm a logged-in user, When I reach checkout with previously saved payment methods, Then I should see my saved cards as options, And I can select one with a single click, And the form auto-fills payment details. Include edge cases: expired cards, declined payments, first-time users. Definition of Ready: story has clear acceptance criteria, designs attached, effort estimated, dependencies identified. Definition of Done: feature tested, documented, deployed, analytics tracking added.

Test API endpoints comprehensively. Approach: 1. Test full request/response cycle. 2. Use real database (test instance). 3. Setup/teardown for clean state. 4. Test authentication and authorization. 5. Validate response schemas. 6. Test error scenarios. 7. Performance testing. 8. Security testing. Use Supertest or similar. Run in CI/CD. Separate from unit tests. Mock external APIs.

Profile and optimize performance. Tools: 1. Chrome DevTools (Performance, Lighthouse). 2. React DevTools Profiler. 3. Node.js --prof and clinic.js. 4. Bundle analysis (webpack-bundle-analyzer). 5. Database query analysis (EXPLAIN). 6. APM tools (New Relic, DataDog). Focus on: render performance, bundle size, API latency, memory usage. Measure before optimizing. Profile in production-like environments.

Establish effective creative collaboration processes for remote and hybrid teams. Communication structure: 1. Daily creative standups (15 min): progress updates, blockers, inspiration sharing. 2. Weekly creative reviews: work-in-progress presentations, feedback sessions. 3. Monthly creative workshops: skill development, trend discussions, team building. Digital collaboration tools: 1. Figma: real-time design collaboration, commenting system, design handoff. 2. Miro: virtual whiteboarding, brainstorming sessions, mood board creation. 3. Slack: creative channels for inspiration sharing, quick feedback loops. 4. Frame.io: video review and approval, timestamped feedback. Creative process adaptation: 1. Async brainstorming: shared boards for idea contribution across time zones. 2. Video critique sessions: screen sharing for detailed design review. 3. Digital mood boards: collaborative inspiration collection. Project handoffs: 1. Detailed creative briefs with video explanations. 2. Asset libraries with clear file organization. 3. Style guides with interactive examples. Cultural considerations: virtual coffee chats, creative challenges, online portfolio reviews for team bonding and growth.

Scan for security vulnerabilities. Tools: 1. SAST (Snyk, SonarQube) for code analysis. 2. DAST for runtime scanning. 3. Dependency scanning (npm audit, Dependabot). 4. Secret detection (GitGuardian). 5. Container scanning. 6. Infrastructure as Code scanning. Integrate in CI/CD. Fix critical issues immediately. Use OWASP Top 10 as guide. Regular security reviews.

Create business model with canvas. Components: 1. Value Propositions (what you offer). 2. Customer Segments (who you serve). 3. Channels (how customers find you). 4. Customer Relationships (engagement type). 5. Revenue Streams (how you make money). 6. Key Resources (assets needed). 7. Key Activities (what you do). 8. Key Partnerships (who helps). 9. Cost Structure (expenses). Use for lean validation and iteration.

Design appropriate sampling strategy and calculate required sample size. Sampling methods: 1. Probability sampling: simple random, systematic, stratified, cluster sampling. 2. Non-probability sampling: convenience, purposive, snowball, quota sampling. 3. Mixed methods: sequential explanatory requires smaller qualitative sample after quantitative phase. Sample size calculation: 1. Continuous outcomes: use power analysis with effect size, alpha=0.05, power=0.80. 2. Categorical outcomes: use proportion formulas with expected proportions and margin of error. 3. Longitudinal studies: account for dropouts, multiply by 1/(1-dropout rate). 4. Cluster sampling: design effect multiplier for correlated observations within clusters. Tools: G*Power, R pwr package, online calculators. Survey research: response rates typically 20-30% for online, 40-60% for phone. Adjust target sample accordingly. Report response rates and compare respondents to non-respondents on available characteristics.

Build financial projections. Components: 1. Revenue forecast (customers × price × conversion). 2. Cost of Goods Sold. 3. Operating expenses (fixed + variable). 4. EBITDA and net income. 5. Cash flow statement. 6. Balance sheet projections. 7. Break-even analysis. 8. Scenario modeling (best/worst/realistic). Use conservative assumptions. Update monthly. Essential for fundraising.

Create compelling pitch deck. Slide structure: 1. Problem (pain point). 2. Solution (your product). 3. Market Opportunity (TAM/SAM/SOM). 4. Product Demo. 5. Business Model. 6. Traction (metrics, growth). 7. Competition (differentiation). 8. Team (why you). 9. Financials. 10. Ask (amount raising, use of funds). Keep to 10-15 slides. Tell a story. Practice delivery. Visual over text.