Results for “ttl”

Drafts time-limited policy-limits demand letters that create an opportunity-to-settle record for third-party bad faith exposure. Use when the user mentions time-limited demand, policy limits demand, bad faith notice, Stowers demand, civil remedy notice, failure to settle demand, excess exposure letter, insurer settlement opportunity, or needs help with acceptance mechanics for a policy-limits offer. Also trigger for Georgia O.C.G.A. § 9-11-67.1 compliance, Florida statutory bad faith prerequisites, or documenting insurer refusal to settle.

The English summary is being prepared. Showing the original description.

One-question-at-a-time design interrogation. Use when: 'grill me', 'interrogate this', 'one question at a time', 'brainstorm', 'let's brainstorm', 'let's discuss', 'lets discuss', 'discuss', 'walk me through', or design review start. Produces ADRs and glossary as decisions settle. Use for unsettled designs; for settled designs go straight to architecture-mode. When the design is unsettled and also has high ambiguity, several technical approaches, or security/data risk, load architecture-mode alongside.

The English summary is being prepared. Showing the original description.

Plan manufacturing jobs around available machines, operators, materials, and delivery dates. Use bottleneck analysis, changeover planning, and workload balancing to compare production sequences and revise schedules when breakdowns, shortages, or absences disrupt the plan.

• Sequence jobs competing for limited equipment
• Revise production schedules after equipment breakdowns
• Compare batch sizes and changeover costs

Find CSS and JavaScript that delay a page’s first visible content. Confirm the bottleneck with browser tools or performance data, then adjust loading behavior and inline essential styles to help the page start rendering sooner.

• Investigating a blank screen during page loading
• Reviewing CSS and JavaScript loading behavior
• Inlining styles needed for the initial display

Work through project decisions one question at a time, with a recommended answer and a short explanation. Record settled choices in project documentation, including scope, completion criteria, constraints, risks, and unresolved questions.

• Clarify project goals through a decision interview
• Agree on deliverables and completion criteria
• Record settled decisions in project documentation

Optimize scientific Python workloads for NVIDIA GPUs by choosing suitable libraries and reducing bottlenecks. Compare outputs with the CPU version and measure complete processing time, including data transfers, to determine whether the GPU implementation provides a useful improvement.

• Assess whether slow Python processing would benefit from a GPU
• Move NumPy or pandas workloads to suitable GPU libraries
• Validate GPU results against CPU outputs

Implement controlled retries and request throttling for external APIs. Covers retryable errors, provider-specified waiting times, increasing delays with random variation, retry limits, and checks that repeating a request will not cause unintended duplicate changes.

• Handle 429 and temporary server errors
• Respect Retry-After waiting times
• Limit outgoing API request frequency

Design systems where multiple AI agents share work, generate tool schemas that define tool inputs for Anthropic and OpenAI, and analyze execution logs. Outputs include role assignments, communication diagrams, and recommendations for addressing cost, latency, and failures.

• Designing agent roles for research automation
• Choosing how multiple agents coordinate work
• Generating and validating tool schemas

Track competitors’ products, pricing, and customer wins or losses, then turn findings into sales comparison sheets, market positioning updates, and feature gap summaries that inform product planning and leadership decisions.

• Mapping direct, indirect, and emerging competitors
• Preparing competitor comparison sheets for sales calls
• Analyzing why deals were won or lost

Turn company strategy into operational plans through process design, OKRs—objectives paired with measurable results—and regular reviews. Produce bottleneck analyses, efficiency scorecards, meeting schedules, and readiness reports for teams preparing to grow.

• Connecting company goals to department and team OKRs
• Finding process bottlenecks and planning improvements
• Assessing operational readiness for team growth

Review game code for likely performance bottlenecks in processing, memory, rendering, and data loading. Compare available estimates with configured limits and produce ranked optimization recommendations, including expected impact, effort, risks, and areas needing runtime measurement.

• Finding performance bottleneck candidates in one game system
• Reviewing performance across the whole game
• Comparing available estimates with configured performance limits

Maintain personal goals and beliefs with timestamped backups, or analyze project documents to connect problems, goals, strategies, and projects. Turn findings about progress, bottlenecks, and alignment into reports, presentation points, or interactive dashboards.

• Update personal goals while preserving history
• Find project dependencies and bottlenecks
• Prepare key points for a presentation

Set up application monitoring with structured logs, performance metrics, and traces that follow requests across services. Build dashboards and alerts, run load tests, investigate CPU and memory bottlenecks, and estimate future infrastructure capacity.

• Set up application dashboards and alerts
• Investigate production issues using logs, metrics, and traces
• Run load tests before traffic increases

Record dated developments in litigation matters and update the corresponding matter log. Capture status, risk, deadlines, and settlement developments, with proposed history entries and field changes shown for review before saving.

• Recording hearings, orders, and new deadlines
• Updating risk assessments after new facts emerge
• Logging settlement offers and authority changes

Maintain data retention in ClawHub's Convex tables by classifying each table, defining expiration fields, and bounding cleanup jobs. Guide changes to temporary data and expired authentication records, with focused tests and runtime verification.

• Classify retention policies for new tables
• Add expiration fields and indexed cleanup
• Update scheduled jobs with bounded deletion batches

Build a concise sales card for competing against one rival using public evidence. Organize talking points, questions, pricing, and claims to avoid, with sources, dates, and labels distinguishing facts, inferences, and assumptions.

• Prepare for sales conversations against a recurring competitor
• Rebuild an outdated sales comparison card with sources
• Develop questions backed by documented competitor limitations

Create and manage prediction markets on Solana, where participants trade YES or NO outcome tokens. Support includes direct peer bets, social media metrics, custom result authorities, market settlement, and redemption of winning positions.

• Create a prediction market around social media metrics
• Build direct peer-to-peer betting markets
• Let an AI agent determine market outcomes

Assess login and verification code protections, identify response differences that reveal registered accounts, and distinguish visible blocks from silent throttling. The skill guides evidence gathering to verify weaknesses and assess their practical impact.

• Review login attempt limits
• Assess OTP and password reset protections
• Check whether responses reveal registered accounts

Guide cache implementation and code reviews by choosing expiration times, update rules, keys, and storage layers. Address stale data and bursts of requests when cached entries expire, with examples for Redis, HTTP headers, and TanStack Query.

• Choosing cache expiration and invalidation rules
• Reviewing cache keys for missing parameters
• Investigating stale data and request bursts

Research technology and advanced manufacturing investments by tracing supply chain bottlenecks, or inputs that are hard to expand. Compare companies using dated evidence, potential earnings contributions, and conditions that would change their research priority.

• Finding companies to research within a technology theme
• Testing claims about a company's supplier position
• Comparing investment candidates across supply chain layers

Choose approaches for prime number problems, including primality testing, factorization, and prime distribution. The skill outlines relevant algorithms and theorems, with commands for symbolic calculation and checking mathematical claims.

• Choosing a primality testing method
• Selecting a factorization approach
• Studying prime distribution and gaps

Use when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch — battle cards vs each named alternative (where we win / where they win / trap questions, every fact traceable), a sales talk track derived from the PR-FAQ spine, an objection-handling table (objection → response → evidence), internal FAQ + CS macros, and an internal launch announcement with embargo discipline. Not for the external message house — use message-house-builder; not for competitor tracking itself — use competitor-tracker or competitor-analysis; not for outbound sequences — use cold-outbound-sequencer. 销售赋能/battle card/销售叙事/异议处理/内部FAQ

The English summary is being prepared. Showing the original description.

Generate intense fight scene and action sequence video prompts for Seedance 2.0 on Higgsfield. Use whenever the user wants fight scenes, combat, martial arts, battles, action choreography, sword fights, hand-to-hand combat, chase scenes, superhero action, or any high-energy action video. Triggers on: fight, combat, battle, martial arts, action scene, choreography, duel, sword fight, kung fu, chase, brawl, punch, kick, weapon combat, superhero fight, or any action/fight request. Use even for "make an intense action video" or "epic battle.

The English summary is being prepared. Showing the original description.

Expert blueprint for Battle Royale games including shrinking zone/storm mechanics (phase-based, damage scaling), large-scale networking (relevancy, tick rate optimization), deployment systems (plane, freefall, parachute), loot spawning (weighted tables, rarity), and performance optimization (LOD, occlusion culling, object pooling). Use for multiplayer survival games or last-one-standing formats. Trigger keywords: battle_royale, zone_shrink, storm_damage, deployment_system, loot_spawn, networking_optimization, relevancy_system, snapshot_interpolation.

The English summary is being prepared. Showing the original description.