'solid' 검색 결과

Review Apache ShardingSphere pull requests or authorized downstream changes using repository evidence. Assess code correctness, merge readiness, or CI failures, then produce consolidated findings or a ready-to-copy reply to a review discussion.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review code changes for correctness and regression risks
• Assess whether a pull request is ready to merge
• Investigate CI failures

Create or improve unit tests for Apache ShardingSphere classes. Cover the target class’s behavior and affected branches, verify explicitly requested coverage goals, and consolidate suitable scenarios into parameterized tests, which run the same checks with different inputs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add missing unit tests for a target class
• Verify an explicitly requested coverage target
• Consolidate suitable tests with different input data

Design persistent agent memory that retains knowledge across sessions and retrieves relevant facts when needed. Compare storage approaches, track people and changing information, and plan memory consolidation and evaluation based on the kinds of questions the agent must answer.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Retain user preferences across conversations
• Track people and entities consistently across sessions
• Retrieve facts valid at a specific point in time

Use grep text searches to locate Solidity code that needs security review. Ten search groups, priority tiers, and protocol-specific patterns help organize findings and choose where to begin a deeper smart contract audit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Mapping review targets before a smart contract audit
• Searching for a specific vulnerability class
• Prioritizing suspicious code for deeper review

Turn an outline or Markdown document into presentation slides with oversized bold text and solid color backgrounds. Preserve the original wording and order, choose a black, red, or yellow theme, and receive a self-contained HTML file.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn a speech outline into slides without rewriting it
• Present a manifesto with oversized text and solid colors
• Create an HTML presentation with a consistent color theme

Build Web3 applications, combining blockchain contracts with a user interface, in a defined sequence. Organize directories, define interfaces, implement and test contracts, configure wallet connections, build components, and prepare deployment scripts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a Web3 project's directory structure
• Defining interfaces for external protocol integrations
• Building wallet-connected contract interaction screens

Writes, reviews, and debugs property-based tests, which generate inputs to check general rules. Helps test conversions, parsers, normalization, and state invariants, assess whether existing assertions are meaningful, and distinguish faulty rules from implementation bugs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing encode/decode round trips across generated inputs
• Checking normalization and sorting properties
• Reviewing whether existing property tests assert meaningful rules

Review smart contract projects against Trail of Bits development guidelines. Examines architecture, upgrade mechanisms, implementation, dependencies, and tests, then provides system documentation, identifies gaps, and recommends improvements in priority order with code references.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review smart contract architecture
• Check upgrade and proxy designs
• Identify gaps in specifications and documentation

Review a pull request using repository checks, verified code references, and current official documentation. Assess correctness, security, structure, and unnecessary code, then post one consolidated GitHub review with inline findings and an evidence-based verdict.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a pull request before merging
• Check code structure and unnecessary comments
• Verify dependency changes against official documentation

Map a codebase into architectural components, logical groups of source files, and compare their sizes using executable statements and file counts. Produce an inventory, identify unusually large or small components, and recommend where to split or consolidate code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a component inventory before splitting a monolith
• Find components with disproportionately large amounts of code
• Review small components for consolidation

Find classes left in parent folders or namespaces and identify nested component structures. Compare consolidation, splitting, and shared code extraction, then plan and carry out refactoring with updated references and tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find classes left in parent namespaces
• Compare consolidation and splitting of nested components
• Move shared utilities into a dedicated component

Create flat SVG illustrations of long-legged people in design and coding scenes. Large black shapes, bright colors, and consistent poses give onboarding screens, error pages, and marketing cards a shared visual style.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Illustrations for onboarding screens
• Character art for error pages
• Cards showing design and coding work

Build a scanning entrance for Three.js models, revealing their wire structure before the solid surface appears. Coordinate both layers with one expanding wave, then remove the temporary wires when the animation finishes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Introduce a 3D model with a radial scan
• Show a model's structure before its surface
• Create a holographic assembly effect

Add a white, twinkling dotted trail that follows the mouse behind website content. The skill guides WebGPU rendering, which uses the graphics processor, with static backgrounds for unsupported devices and accessibility preferences.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add a mouse-following trail to a hero section
• Create an interactive contact section background
• Keep a static background on touch devices

Create simple, cute square character images using rounded shapes, two character colors, and a solid background. The skill can use product context to propose three design directions and generate six separate candidates for comparison.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a product mascot
• Compare three character design directions
• Simplify an animal or object into a recognizable character

Find repeated interface elements and shared visual values, then turn them into reusable components and design tokens, named values for colors or spacing. Update existing uses and document the additions within the project's design system.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Consolidating repeated buttons and cards
• Turning colors and spacing into shared tokens
• Unifying inconsistent interface components

Analyze an organization's sub-transaction patterns in TRES Finance, identify groups of repetitive transactions, and propose data-driven rollup rules that consolidate them into one aggregated entry per interval (daily or monthly) for cleaner ERP integration. Also lists and deletes rollup rules. Trigger this skill whenever the user asks about rollup rules, transaction aggregation, consolidating transactions, reducing transaction noise, rolling up gas fees, rolling up staking rewards, rolling up micro-transactions, or collapsing many small ledger entries into fewer summary entries. Also trigger on "create a rollup rule", "suggest rollup rules", "what should I roll up", "show my rollup rules", "delete a rollup rule", "aggregate transactions", "too many transactions", "reduce transaction count", "roll up fees", "daily rollup", "monthly rollup". If a wallet has too many transactions, high-frequency activity, or noisy ledger entries, proactively suggest rollup rules. For computing the EXACT impact of a single already-specified rule or reviewing submitted/pending rules, use the tres-rollup-review skill instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Promote existing research into a stable-status canonical article under `articles/` in a Knowledge Base project (the `knowledge-base` starter pack). Read when a decision has actually been made and the team wants the source-of-truth written down, or when asked to consolidate, canonicalize, promote research, or supersede an older article. Carries the decision-confirmation gate, the `supersedes:` chain that keeps the evidence trail intact, and the canonical voice. Does not conduct new research — that is the sibling `research-with-sources` skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Recall past facts, preferences, and decisions from ReMe; inspect memory delivery, service health, and the consolidation schedule; or consolidate memory when requested.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit whether the organisation's AI spend actually paid — measured against baselines, not vendor math or vibes. Use when a CFO asks what the AI tools returned, when renewing AI contracts, when consolidating overlapping AI subscriptions, or to build the measurement plan before the next spend. Produces an ROI audit with per-tool verdicts (keep/consolidate/cut), the honest-measurement method behind each number, and a baseline plan for whatever can't be scored yet. To forecast ROI before an investment use roi-estimator; this skill measures what already happened.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Consolidate all SAST vulnerability results from the sast/ folder into a single final report ranked by severity and confidentiality impact. Reads all *-results.md files and produces sast/final-report.md. Run after all vulnerability detection skills complete. Use when asked to generate a final report, consolidate findings, or summarize security results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Convert English-language properties in PROPERTIES.md (produced by the Fizz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes. Trigger on "fizz-convert", "convert properties", "implement properties from PROPERTIES.md", "convert PROPERTIES.md to Solidity".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.