Diagnose and fix common AppFolio API integration errors. Trigger: "appfolio error".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
384건 · 관련도순
Diagnose and fix common AppFolio API integration errors. Trigger: "appfolio error".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Optimize AppFolio API costs through efficient usage patterns. Trigger: "appfolio cost".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Secure AppFolio API credentials and tenant data. Trigger: "appfolio security".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Handle AppFolio API rate limits with throttling and backoff. Trigger: "appfolio rate limit".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Collect AppFolio API debug evidence for support tickets. Trigger: "appfolio debug".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate tenant management and lease operations with AppFolio. Trigger: "appfolio tenant management".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply production-ready patterns for AppFolio REST API integration. Trigger: "appfolio patterns".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy AppFolio integration service to cloud infrastructure. Trigger: "deploy appfolio".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Query AppFolio properties, units, and tenants via REST API. Trigger: "appfolio hello world".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Production readiness checklist for AppFolio integrations. Trigger: "appfolio production checklist".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Testing strategies including contract testing, snapshot testing, mutation testing, property-based testing, and test organization
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write Unreal Engine 5 C++ gameplay code: the UCLASS/UPROPERTY/UFUNCTION reflection macros, the Gameplay Framework (GameMode, Pawn, Character, PlayerController, Actor components), and the module Build.cs. Use when writing or debugging UE C++, deriving from AActor/ACharacter/ AGameModeBase, exposing properties to the editor or Blueprints, or when the user mentions Unreal C++, UCLASS, GENERATED_BODY, GameMode, ACharacter, or .Build.cs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness. Use this to review a contract or commitment, assess regulatory or privacy exposure, evaluate an IP or licensing question, judge the risk in a business decision, prepare for an audit or certification, or when a plan may create obligations the business cannot meet. Also use to decide whether a risk should be accepted, mitigated, or refused.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Covers what the organization owns and what it is only borrowing — trademarks and clearance, copyright and work-for-hire, patents and trade secrets, open-source license obligations and copyleft reach, and IP terms in customer, contractor and AI-tool agreements. Use this to check whether a name is usable, establish that you own work you paid for, decide how to handle a license obligation in a dependency, or respond to an infringement claim.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to perform actions inside an Unreal Engine project via a live-editor MCP connection. Trigger when the user wants to change, query, or run something in their Unreal Engine project, not for conceptual or docs questions. Concrete triggers: spawn/move/duplicate/transform actors in a level, open a `.uproject`, add things around a PlayerStart, create or edit a Blueprint/Widget/Material/Niagara/Control Rig/Sequencer/Behavior Tree/GAS ability, read or write properties on actors (e.g. `bIsLocked` on `BP_DoorActor`), Live Coding recompile after editing C++ (`AActor`, `UMyComponent::Method`, `UPROPERTY`), or modify Static/Skeletal Mesh assets. Treat as Unreal context even without the word "Unreal": asset prefixes `BP_`, `WBP_`, `M_`, `MI_`, `NS_`, `CR_`, `SK_`, `SM_`, `ABP_`; UE C++ types/macros; `.uproject`; Content Browser; Outliner; PlayerStart; "in my game" plus UE signals. Skip for: pure conceptual/docs questions, Unity, Godot, or unrelated uses of "blueprint"/"sequencer"/"widget".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when deciding what characterization and experimental detail an Advanced Materials manuscript must show to prove its structure–property claim, and what belongs in the Experimental Section and Supporting Information. Partitions and stress-tests methods; does not design figures or run analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when revising an AAMAS paper so the interaction contribution leads the first page, the solution concept or incentive property is named, the game and agents are legible, claims are paired with proofs or multiagent experiments, the argument fits eight two-column pages plus references, and the wording stays double-blind.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate Echidna/Medusa-compatible Solidity fuzz suites from Foundry or Hardhat projects. Trigger on "fizz", "generate fuzz suite", "build fuzz harness", "stateful fuzzing", "fuzzing harness", "property testing", and "invariant suite".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Governs Event Schema Sets, the Fabric registries of event types and message payload schemas. Covers create, rename, update and delete of a definition, and listing, property reads or base64 decoding. Every Event Schema Set task belongs here. Ingestion pipelines are eventstream-cli.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Publish .NET services as container images with the built-in SDK tooling (dotnet publish /t:PublishContainer, Microsoft.NET.Build.Containers) - no Dockerfile required. Covers the MSBuild property surface, base-image inference, self-contained and AOT implications, and CI/CD publishing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write and simplify C# property-based, model-based, and executable specification tests with CsCheck. Use for generators, shrinking, stateful command sequences, Spec guards and rules, implementation conformance, or replaying generated failures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement Swift Codable models for JSON and property-list encoding and decoding with JSONDecoder, JSONEncoder, CodingKeys, and custom init(from:) or encode(to:). Use when parsing API responses, remapping keys, flattening nested JSON, handling date or data decoding strategies, decoding heterogeneous arrays, or integrating Codable with URLSession, SwiftData, or UserDefaults.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply modern Swift language patterns and idioms for non-concurrency, non-SwiftUI code. Covers if/switch expressions (Swift 5.9+), typed throws (Swift 6+), result builders, property wrappers, opaque and existential types (some vs any), guard patterns, Never type, Regex builders (Swift 5.7+), basic Codable shaping (CodingKeys, custom decoding, nested containers), modern collection APIs (count(where:), contains(where:), replacing()), basic FormatStyle usage, and string interpolation patterns. Use when writing core Swift code involving generics, protocols, enums, closures, or modern language features; route deep Codable to swift-codable, detailed formatting/localization to swift-formatstyle, and API naming to swift-api-design-guidelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TikTok Shop policies and compliance — restricted products, intellectual property, content guidelines
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.